Cortex Code - Cortex Docs

Cortex Code changes repositories. You describe the work, the agent carries it out inside a runtime prepared for that repository, and every step lands on a timeline you can read and stop. It is available in the web app, the desktop app, and the CLI, with one account across all three.

Cortex Code feature grid — One repository per runtime, Reviews that stay failed when they fail, No pasted diff, The same account as Chat — The four commitments on the public Code page: one repository per runtime, reviews that stay failed when they fail, no pasted diff, the same account as Chat.

What Code is

Commitment	What it means for you
One repository per runtime	Each session gets an isolated guest on the same farm as Cortex Bot, without a desktop. The environment is installed by the agent, not guessed from a filename.
Reviews stay failed when they fail	A Cortex Security review is one pass over a diff. A failed review is stored as failed — never rewritten as an approval.
No pasted diff	Code writes the change in the repository; Cortex Security reads the pull request in place. Neither asks you to paste a patch into a box.
The same account as Chat	Sign in on cortex.foundation. No second identity.

Who can open it

Code is a member surface. A guest visiting /code sees the public product page, and deep links show This space is reserved with Continue in Chat or Sign in. Once signed in, /code opens Code Home: connect GitHub, pick a repository, start a session. See Accounts.

Where it runs

Surface	Host	Notes
Web app	Cloud	Web Code is Cloud-only
Desktop app	Cloud, This PC, SSH	Code on desktop
CLI	Cloud by default; This PC and SSH by opt-in	Code in the terminal

What Code is not

Not this	Use instead
A Chat transcript	A session is a turn timeline — files read, edits, commands, plans
Chat’s Python sandbox	Cloud runtimes — an isolated guest with your repository
A Chat plugin	Connect GitHub — the repository connection lives in Code
The public `/security` page	Cortex Security — the signed-in review inbox at `/code/security`
A place to store secrets	There is no Secrets page. Environment for a guest belongs to that guest; `/code/secrets` sends you home.

Modes in one line

Ask reads and explains. Plan proposes without changing anything. Agent edits files and runs commands. Pick per turn; the session row holds the default. See Ask, Plan, Agent.

Next

Code quickstart — first session in the web app.
Sessions — reading the timeline.
CLI — the terminal front-end to the same sessions.

⌘I