Your first task

Once Kodik is installed and you are signed in, you are ready to go. This page walks you through one complete cycle: request → execution → reviewing changes.

Step 1. Open a project folder

Go to File → Open Folder and pick your project directory. Kodik works with any language or project type; you do not need existing source code — an empty folder is fine to start.

Step 2. Open the chat

The AI panel is on the right side. If it is hidden, reveal it and focus the chat input with Ctrl+Alt+C / Cmd+Alt+C, or click the Kodik icon in the Activity Bar.

Step 3. Choose a mode

The mode switcher sits at the bottom of the chat. The default is Code — the agent immediately gets to work: reading files, writing code, running commands.

For a complex task where you want to discuss the approach first, switch to Plan. In Plan mode the agent creates a detailed implementation plan without touching any files. When the plan looks good, switch back to Code and say “go ahead”.

Toggle the mode with Ctrl+Shift+A or by clicking the mode name.

See Modes for a full description of all five modes.

Step 4. Send a request

Type your task in the input field in plain language and press Enter. For example:

• Add email validation to the registration form
• Write tests for the parseDate function
• Explain how the auth module is structured

Dictate a request

The primary chat input has a microphone immediately to the left of Send. Click it to start voice input, then click it again to stop and keep the transcript in your draft. Press Escape while recording to cancel and restore the exact draft you had before recording. Voice input never sends automatically—you can review and edit the transcript before pressing Enter or Send.

Voice input currently uses the speech provider registered with the IDE. If no provider is available, Kodik keeps your draft unchanged and shows an availability error instead of capturing audio.

The agent starts working immediately — you will see a live stream of actions: reading files, searching the codebase, writing changes. Every step appears in the chat as it happens.

If the internal connection between chat and the workbench is interrupted, Kodik reconnects it automatically. Reconnecting… appears above the composer while the transcript and task status catch up; the task keeps running, and Kodik does not resend a message the workbench already accepted. If one stored or streaming message is malformed, Kodik isolates that row and keeps the rest of the transcript and composer usable.

If a request uses your remaining credits, Kodik shows Usage limit reached even when the service returns no chat message. After you add credits and dismiss the warning, starting the next turn does not reopen the old zero-credit warning; a fresh zero-credit response will show it again.

Step 5. Review the changes

When the agent finishes, a changes panel appears in the chat. It shows how many files were affected and how many lines were added or removed.

• Click a file name to open the diff in the editor.
• Click Accept (or accept all) to apply the edits.
• Click Reject to revert changes in that file.

See Reviewing Changes for more detail.

Next steps

• Modes — how Code, Plan, Ask, Debug, and Educator differ
• Reviewing Changes — how the diff panel works
• Auto-approve — let the agent work without pausing for confirmation