Skip to main content
The extension puts coding sessions, tool activity, approvals, and diff review alongside your source files in VS Code. The separate Chat and Usage views are available in the desktop app. Download the VS Code package for your operating system and processor. These links point to MKA1 Code 1.57.4. If your organization provides its own distribution, follow the organization download steps and choose the VS Code package.

​
Install the extension

Download the platform-specific .vsix file. In VS Code, run Extensions: Install from VSIX… from the Command Palette and select the file.

​
Start a session

  1. Open your project folder in VS Code.
  2. In the Command Palette, run MKA1 Code: Open.
  3. If prompted, choose Sign in and complete authorization in your browser, or choose API key and validate your key against the configured gateway.
  4. Start a session and choose a model. Open + → Draft a plan to investigate an approach before editing. Review the proposal and choose Implement the plan when you are ready to proceed.
For the checkout example, keep the failing test or calculation open beside the conversation. The panel streams responses and shows tool activity, diffs, and context usage as the agent works. Answer questions and approval requests there, then run MKA1 Code: Review changes to inspect the edits before committing them. You can resume a session or branch its conversation from an earlier message to explore another approach. The extension also lets you prepare a Git branch or worktree for the session. Conversation branches preserve different discussion histories; Git branches and worktrees manage the repository changes. In the settings view, Extensions lets you manage MCP connectors and compatible plugin packages. These settings are shared with the desktop app and CLI when they use the same local store.

​
Work through a change in the editor

Keep the relevant source or test file open beside the agent panel. Mention the file in your request and define the expected result, for example: “Add a regression test for three checkout items, fix the calculation, and run the tests.” Expand tool activity to verify the command output, then use MKA1 Code: Review changes to inspect the implementation and test together. To stop a run, use MKA1 Code: Interrupt run. To begin a different task, use MKA1 Code: New session and check its folder and branch before sending. Opening a new conversation does not isolate repository files; choose a worktree when two tasks need independent working copies.

The MKA1 Code panel in VS Code shows command activity and the test result.

​
Configure and troubleshoot

Run MKA1 Code: Settings or open settings from the extension header. Check access, connection, and the default model. Save connection changes before testing another request. If your distribution uses a different product name, its Command Palette entries use that name. A connector may require browser authorization before tools appear. In a remote VS Code session, follow any instruction to complete that connection in the desktop app or local terminal. Desktop-only controls, such as integrated document previews and conversation follow-up schedules, are covered in the desktop guides rather than this extension workflow. Continue with Usage and troubleshooting.