
Terminal
Run ctx in any repository and keep the full workflow in your shell.
Give Context a repository task. It reads the code, makes changes, runs commands, and returns a diff for review.
Private preview for macOS, Linux, and Windows through WSL.

Repository work

Start Context in a repository and describe the result you need in plain language.
Context shows the files it reads, the commands it runs, and the changes it makes as the task progresses.
Inspect the result, ask for another change, or open a pull request with the completed work.
One run, three surfaces

Run ctx in any repository and keep the full workflow in your shell.

Review the plan, file changes, and command output beside the code.

Start a run in the browser and continue it from the command line.
Your controls
Context follows your project rules, scripts, and review requirements in every run.
Choose which files, commands, networks, and connected systems a run can use.
Use the models approved by your organization without changing the CLI workflow.
Keep prompts, tool calls, command output, sources, and changes together for review.
Works with the tools already in your workflow
Context CLI
Tell us about your repositories, infrastructure, and review process. We'll confirm preview availability and help your team get set up.
Request preview accessmacOS, Linux, and Windows through WSL.
It can read and explain code, edit files, run commands and tests, and prepare a diff or pull request for review.
Only the files, commands, network destinations, and connected systems allowed by your repository and organization settings.
No. Model choices follow your organization's Context settings, so teams can use approved models without changing their command-line workflow.
Yes. Context supports hosted, customer-cloud, on-premises, and fully air-gapped deployments.
Yes. Desktop, web, editor, and CLI runs share the same permissions, repository context, and traces.