Nakka

An AI coding agent in your sidebar — and you decide how much it may do on its own.

Nakka reads your code, searches it, runs commands and makes edits. What it does without asking is a setting, not a surprise.

You choose how much rope it gets

Switch with Shift+Tab, or from the mode chip in the input bar.

Auto does not mean "anything". Every command is classified before it runs:

• npm test, pytest, git status, npm install — runs
• rm -rf, kill -9, git push --force — stops and asks, in every mode
• Anything catastrophic — refused outright, in every mode, including Auto

Plan mode is enforced, not advisory. While a plan is being written, edits are refused by the permission layer, and only the plan file may be written. Approving the plan is what unlocks the work.

What it can do

Read and search. Open files, grep across the tree, glob for paths, follow a codebase it has never seen.

Edit. Exact-match edits, applied to your editor as a diff you accept or reject. In Auto, accepted for you. The file is re-read before the edit lands, so an edit never overwrites a change you made while the prompt was on screen.

Run commands. Output streams back as it arrives. A command that outlives its timeout is moved to the background and handed to you with an id, not killed — a build that takes three minutes is not a build that failed. A dev server started in the background returns immediately instead of hanging the turn.

Ask you. When a choice is genuinely yours — which database, which auth method — it asks in the transcript, with the options side by side, and a field for an answer that was not on its list.

Track its own work. A task list you can watch it move through, so a long job is legible while it runs.

Notebooks, web fetch, and sub-agents for work that deserves its own context.

Bring your own model

You bring the key. There is no account, no sign-in and no proxy: requests go from your editor to the provider you configured.

Getting started

1. Install the extension and open Nakka from the activity bar.
2. Add a model and its API key when prompted, or write ~/.nakka/config.yaml yourself.
3. Ask it something about the code you have open.

Start in Manual to see how it works. Move to Auto once you trust it.

Configuration

~/.nakka/config.yaml:

models:
  - name: Sonnet
    provider: anthropic
    model: claude-sonnet-4-6
    apiKey: sk-ant-...
    roles: [chat, edit, apply]

  - name: Local
    provider: ollama
    model: qwen2.5-coder:7b
    roles: [chat, edit, apply, autocomplete]

Project rules. Nakka reads AGENTS.md, AGENT.md or CLAUDE.md from your repository root, and any .md file under .nakka/rules/, as standing instructions for that project.

Privacy

No telemetry. Nakka collects nothing and sends nothing anywhere except the model provider you configured, using the key you supplied. Your code goes to that provider and nowhere else.

Licence and origin

Apache-2.0. The licence and the attribution notice ship inside the extension as LICENSE.txt and NOTICE.

Nakka is a fork of Continue, also Apache-2.0. The files have been changed substantially — NOTICE sets out what was changed. Continue Dev, Inc. does not endorse this extension and is not connected to it.

Provider names and logos shown in the model picker are the marks of their owners and are used only to identify those services.