Start here

What ContextCode Beta is

The optional ContextStream coding agent for your terminal, available in beta.

ContextCode is a terminal coding agent in beta. It is optional: you do not need it to use ContextStream, and the production path remains connecting the assistant you already use through the ContextStream MCP.

In the beta, you type csc, describe what you want, and ContextCode plans, edits, runs the build, and shows you the diff.

The same partnership model applies here: you set the goal, constraints, and permission boundary; ContextCode chooses the investigation and permitted next steps; ContextStream supplies the scoped evidence and continuity. You should not need to coach every lookup.

What separates it from a chat window is that it starts every session already grounded in the project history that was actually saved — decisions, lessons, plans, captured sessions, and the shape of the indexed codebase. Approved plans and explicit saves feed that history back. The second week can be better than the first without pretending every passing sentence became memory.

“add rate limiting to the API”

A plan you can approve, then the edits, then the tests.

“what did we decide about retries?”

The answer, from your own past sessions — not a guess.

“run the build in the background and keep going”

The build runs across turns; you keep working.

“that was wrong, undo it”

Every file the turn touched, restored.

What it can do

Write code. Plan, edit, run tests, read output, fix, repeat. Permission rules decide how much of that happens without asking you.

Work in parallel. Send a task to a background agent and carry on. Or hand it a whole goal and let a planner split it into pieces that several agents take at once, each on its own branch, with a reviewer at the end.

Remember. Approved plans and decisions or lessons you explicitly save resurface when they're relevant — in this session, next month, or on another machine. Captured exchanges and snapshots add continuity. Ask "what did we decide about X" and get an answer from the records that exist.

Stay reversible. Every turn is a checkpoint. /undo puts the files back. /worktree moves the whole session onto an isolated branch and /worktree done merges it home.

Check its own work. /review reads your changes against your project's recorded conventions before you commit. /verify drives a real browser through a feature and comes back with screenshots and a verdict.

Use whatever model you want. The managed default routes each part of a job to a suitable frontier model and bills credits. Or bring your own key for any provider and the turns bill to you instead.

What it isn't

It isn't a hosted IDE, and it isn't a chat window with a code block in it. It edits files on your machine, runs your commands, and leaves a diff and checkpoint trail you can review. It does not commit unless you ask it to.

It doesn't need API keys pasted anywhere to get going. csc login opens a browser once, and that's the whole setup.

How ContextCode Beta fits with everything else

ContextCode Beta is an optional client over the same ContextStream platform the production MCP exposes to supported assistants. Beta sessions can contribute durable project records and captured continuity, but ContextCode is not the default onboarding path or a requirement for the MCP product.

See how the agent partnership works for the production platform model and its limits.

Next