YAGNI Code for VS Code
YAGNI Code in your editor. The same agent you get from the yagni command, in
a side panel that knows which file and selection you are looking at.
This is a beta. It works end to end today and it will keep changing. If
something gets in your way, tell us at yagni.app.
Before you start
A YAGNI account. Sign up at yagni.app.
The YAGNI Code CLI, signed in. The extension drives the CLI installed on
your machine, so your account, budgets, model tiers, permission rules and
connected tools all come from that install:
npm install -g @yagni-app/code
yagni login
Node.js 22.19 or newer on your PATH, which the CLI needs anyway.
A folder open in VS Code. The agent works inside a repository.
What it does
- Session panel. Streaming replies, tool cards, the agent's checklist, and
the same permission prompts the desktop app shows, inline.
- Editor context. Each message you send carries the active file and your
selection, so "fix this" while pointing at code means something. The chip
above the composer shows what will be attached; click it to stop attaching.
- Review changes. The panel counts the files the agent edited. Click the
count, or run YAGNI Code: Review Changes, to open each one in VS Code's
diff editor against HEAD.
- Resume. Pick up an earlier session from this repository, including ones
you started in the terminal or the desktop app. The picker shows sessions
from the CLI's active profile (
yagni profiles); a session always resumes
under the profile it was started in, never through another one's
credentials.
- Open as editor tab. The same panel at full width when you want more room.
Where it lives
The panel opens in the secondary side bar, on the right, next to your code.
Drag its icon to the left if you would rather have it there; VS Code
remembers. The panel follows your editor's colour theme; pin it to light or
dark with YAGNI Code: Appearance.
Commands
| Command |
What it does |
| YAGNI Code: New Session |
Focus the panel and start a session in the workspace folder |
| YAGNI Code: Open as Editor Tab |
Open the panel beside your editor |
| YAGNI Code: Review Changes |
Pick a file the agent changed and open its diff |
| YAGNI Code: Sign In |
Open a terminal running yagni login |
| YAGNI Code: Appearance |
Match the editor's theme, or pin the panel to light or dark |
Settings
| Setting |
Default |
Meaning |
yagniCode.cliPath |
"" |
Path to the yagni command when it is not on PATH. User settings only; a repository cannot set it |
yagniCode.model |
"" |
Tier for new sessions (efficient, standard, advanced, peak); empty uses the CLI's default |
yagniCode.includeEditorContext |
true |
Attach the active file and selection to each message |
Privacy and trust
Sessions start only in a trusted workspace (Workspace Trust): the agent runs
tools inside the folder. The page inside the panel makes no network requests
of its own. Everything that leaves your machine goes through the yagni CLI,
exactly as it does in the terminal. The extension reads
~/.yagni-code/agent/*/sessions to list sessions you can resume; it never
reads your token.
Ending a session, or closing the panel, ends the whole process tree under it:
the yagni launcher, the agent, and any tool it was running. On macOS and
Linux the tree gets a few seconds to shut down cleanly before it is killed; on
Windows it is terminated outright, since there is no graceful signal to send
through the npm shim.
Not yet
A terminal for the agent's shell, diff tabs inside the panel, a sessions
rail, and a spend readout are on the desktop app and not yet here. Sign-in
happens in a terminal, through the CLI.