BETA RELEASE

Command Code
for your IDE.

Chat, review changes, and run commands without leaving your editor.

Beta for VS Code and Cursor. JetBrains coming soon.

BetaIDE preview

From prompt to patch

Your coding agent, inside your editor.

Ask without switching windows.

Open Command Code from the activity bar and chat right beside your files.

Follow the work as it happens.

See the files your agent reads, the commands it runs, and the agents it starts.

Review in your editor.

Changes open as diffs in your editor, so you keep or revert each one.

Your whole workflow, in your editor.

Keep the chat, agent activity, diffs, and test runs next to the code you are changing.

Chat in your sidebar.

Ask, plan, and switch between saved sessions without leaving the file you are in.

Command Codecommandcode

fix the failing session test, write the v0.3 changelog and add a regression test

All three done. The expired-token branch now returns the refreshed session early, and a regression test guards the fix. 13 tests pass.

Ask Command Code…

Native diffs.

Proposed edits open in the editor, so you can check every line before you keep it.

src › auth › session.tscommandcode
3838export function readSession(token: string) {
3939 const claims = decode(token);
40- if (claims.exp < now()) refresh(claims);
41- return toSession(claims);
40+ if (claims.exp < now()) {
41+ return refreshSession(claims.sub);
42+ }
43+ return toSession(claims);
4244}
4345
4446export function toSession(claims: Claims): Session {
4547 return { user: claims.sub, expiresAt: claims.exp };
4648}

Tool activity.

Every read, edit, command, and agent run is grouped into one receipt you can scan.

Command Codecommandcode

Read 3 files, ran 2 commands, and ran 2 agents

Readsrc/auth/session.ts
Readsrc/auth/session.test.ts
ReadCHANGELOG.md
Ran commandpnpm vitest src/auth --run
Ran commandpnpm typecheck
Ran agentdocs-writer
Ran agenttest-reviewer
Editedsrc/auth/session.ts

Integrate with your editor

Extensions for VS Code, Cursor and JetBrains IDEs.

VS Code & Cursor Beta

In VS Code, search for Command Code in the Extensions view. In Cursor, run cmd --ide-setup from the Command Code CLI. Then open it from your activity bar and sign in.

Free. The same extension works in both editors.

JetBrains IDEs

Next up: IntelliJ IDEA, PyCharm, WebStorm and the rest of the JetBrains IDEs.

Coming soonFollow along on Discord.

//faq

Questions, answered.

Everything that usually comes up before you install the extension. Still curious? Read the docs, or join the Discord.

It is Command Code, now inside your editor. Chat beside your code, review proposed edits as native diffs, and keep working without interruptions.

Visual Studio Code 1.106 or newer and Cursor, in beta today. The JetBrains IDEs are coming soon.

In VS Code, search for "Command Code" in the Extensions view and install it, or get Command Code for VS Code and Cursor from the Marketplace. In Cursor, run cmd --ide-setup from the Command Code CLI, which installs it into every supported editor it finds. Then open it from the activity bar and sign in.

No. The extension only needs a Command Code account. If you already use the CLI, your sessions, taste, skills and MCP servers are shared, so you pick up where the terminal left off. A few terminal-first commands stay CLI-only.

Yes. Command Code IDE extension sees the file you are editing and the lines you have selected, so "fix this" just works, with no paths or line numbers to paste. Type @ to add other files or folders, or attach up to six images. To stop sharing selections, turn off commandcode.context.autoAttachSelection.

This is a beta, so bugs are expected and welcome. Run /feedback, open a GitHub issue with what you did, what you expected and what happened, or come talk it through on Discord.