Kakon for VS Code

From your question
to a reviewed diff.

Read the code. Work out the change. Let Projects handle the steps, with your editor and review in the loop.

Coming 1 December 2026 · No access before launch · VS Code 1.95+

Projects editor panel in Build mode with command approval and Open diff controls.
Editor panel with example content. Diff text opens in the VS Code host.

A mode for the
way you want to work.

Understand first. Plan the change. Build with approval, or allow routine work within your guardrails.

Make the change. Keep the review.

Edit files and run commands after approval. Review the native diff when the run finishes.

Untrusted folders allow Ask only.

Build

Add one retry and check the auth tests.

File context
Available
File edits
Ask first
Commands
Ask first
Git changes
Ask first
You set the direction.
Build mode. Edit files and run commands after approval. Review the native diff when the run finishes.

Your workspace.
A shorter path through it.

Familiar files, terminal output and native diffs. The details stay close to the work.

Context from your workspace.

Work with the active file, selected code, file mentions and diagnostics. Choose the context that helps explain the task.

@src/auth.ts:12–28

The diff is yours to review.

Open the native diff after a run. Accept to keep an edit, or Reject to restore it without overwriting later changes.

Open diff → Accept / Reject

Tools run where the project lives.

Read files, edit code and run approved commands in the editor’s extension host. No desktop companion required.

$ npm test -- auth

A way back into the work.

Reopen run history. Resume an interrupted run when saved pending tools are available; retry a connection without resending your task.

Retry connection / Resume
Folder contextYour taskApprovalReview the diff

Your first question
starts here.

One local folder. Your Kakon account. A small task worth moving forward.

Kakon for VS Code
  • VS Code 1.95 or newer
  • One local, trusted project folder for Build
  • Kakon account with Projects access
Coming 1 December

Coming 1 December 2026. No installation or access before launch.

Open your Kakon account
  1. 01

    Install the extension.

    Coming 1 December 2026. Installation is not available before launch. These steps describe the upcoming workflow.

  2. 02

    Connect your Kakon account.

    Run Kakon: Sign in. Complete browser sign-in, choose Connect editor, then Return to editor. Your account needs Projects access.

  3. 03

    Start with one small task.

    Open Kakon: Get started or Kakon: Open panel. Ask about the code, then try Build and review the change with Open diff.

Know the boundaries.

Designed for one local folder. Remote, virtual and multi-root workspaces are outside the current scope. Untrusted folders allow Ask only.

Local tools. Shared context.

Selected code, unsaved selections, file context, diagnostics and tool results go to Kakon and the model provider. Check what you send; secret masking cannot detect every secret.

Before you open
the next folder.

Is Kakon for VS Code available now?

No. Coming 1 December 2026. The desktop app and VS Code extension are unavailable before launch. Chat is available now.

Does it need the desktop app?

No. The VS Code extension includes its local agent host. Open one local project folder and connect your Kakon account.

Is this typing autocomplete?

Kakon is a coding agent. Give it a task, work through the plan and review its changes. It does not provide typing autocomplete.

Can I use Cursor, Windsurf or VSCodium?

These are compatibility targets, alongside Antigravity. Their installation, browser callback and run acceptance are still pending. VS Code API compatibility alone does not establish support.

What happens when I reject or stop a run?

Reject and checkpoint rewind protect later disk changes. Commands and Git effects can need separate recovery. Stop ends the agent loop, but a command already running in the foreground can finish before stopping.