AGI in VS Code · developer preview

Your editor,with an agenton call.

Mention @agi in VS Code chat. Work with an assistant grounded in your workspace. Run /explain and /tests, review diffs, and hand heavier work to Desktop over an explicit local bridge.

Explore AGI Code See the CLI

@agi · chat participant
Context · workspace-scoped
Handoffs · explicit

In the preview

A focused start, on the suite's rules.

AGI in VS Code ships the way every AGI surface does: visible context, reviewable changes, no silent routing. Here's what works today.

@agi chat

Ask where you're typing.

A chat participant grounded in your workspace.

Reads the active file, selection, and language
Adds diagnostics, open files, and project structure
Pinned files travel with the conversation

Diff review

Changes land on your terms.

Proposed edits arrive as diffs you review first.

See exactly what would change before it touches your files
/fix and /refactor explain every change they propose
You decide what gets applied

Explore AGI Code

Desktop bridge

Heavier work, handed off explicitly.

Pair the editor with AGI Desktop when you choose to.

Local WebSocket bridge on port 8787
Authenticated handshake with allowlisted message types
Degrades gracefully when Desktop isn't running

See AGI Desktop

Slash commands

Six commands, zero context switching.

Type / in the @agi chat to act on your selection: explain it, fix it, test it, document it, or switch the model behind the conversation.

@agi · VS Code chat

/explain   Explain the selection in plain language
/fix       Find and fix bugs in the selection
/refactor  Suggest refactoring improvements, each change explained
/tests     Generate unit tests covering edge cases and error paths
/docs      Write doc comments in the style of the language
/model     Switch the active provider and model

AGI Code

One developer story, two surfaces.

AGI in VS Code pairs with the AGI CLI. Assistance in the editor when you want context and diffs. An agent in the terminal when you want resumable sessions and sandboxed execution. Developer sessions stay separate from consumer chat sync. Every cloud or local handoff is explicit.