What coding agents does Clor run?
Clor runs the official Claude Code and Codex CLIs behind its own web interface. Their native TUIs are also available in web-based terminals.
Still juggling coding agents in terminal tabs?
Ship faster and more reliably with isolated agentic development environments
- Claude and Codex Use your existing subscriptions or API keys with the official agent harnesses
- Shared agent memory Give Claude and Codex access to every live and historical session, with full-text search and a shared agent wiki
- Everything is a CLI command Agents can create spaces, manage resources, and use every Clor service themselves
- Docker isolation Every workspace is an isolated container with its own Git checkout
- GitHub and Linear Agents can manage issues, change code, and open pull requests
- Local and hosted Run spaces on your own Mac or Linux machine, or on a cloud runner
Questions developers ask
What is a runner?
A runner is the machine that runs your spaces. It can be your own Mac or Linux machine, or a cloud runner you create. Each runner manages the containers and processes for the spaces assigned to it.
How do I sign in to Claude and Codex?
Sign in with your existing Claude or OpenAI account, or provide an Anthropic or OpenAI API key. Credentials are automatically synced across local and hosted runners.
Does Clor proxy or resell my model traffic?
No. Clor runs the agent on your selected runner. Claude Code connects directly to Anthropic, and Codex connects directly to OpenAI. Clor does not proxy, resell, or mark up that traffic.
How does space isolation work?
Container-backed spaces have isolated filesystems, processes, ports, dependencies, and Git checkouts. Docker or OrbStack provides the container runtime. On macOS, containers run inside a Linux virtual machine. Spaces can also run directly on a host.
What does space isolation protect against?
Isolation is primarily an operational boundary, not a sandbox for a malicious agent. Prompt injection remains possible, but it is a much smaller practical risk with strong current models. Containers let agents work independently and keep a bad Bash command from deleting files on your computer or trampling another agent's checkout.
How do parallel agents stay out of each other's way?
Each container-backed space has its own checkout, processes, ports, and dependencies. Agents in separate spaces do not share these resources. Agents in the same space share its working tree.
Does Clor use Git worktrees?
No. Clor uses a separate Git checkout and, by default, a separate container for each space. You can create worktrees inside a space if needed.
Does Clor see my code?
The working tree stays on the local or hosted runner executing the space. Clor stores the space configuration, not a copy of its checkout. Agent transcripts may contain code and are stored in memory for session history and search.
What does Clor store, and how do I delete it?
Clor stores agent sessions and wiki documents, Git repositories, Drive files, secrets, and published sites. Delete resources through the CLI or web interface. Session retention depends on your Team tier; wiki documents persist until deleted.
Where do my agent credentials live?
Agent credentials are encrypted at rest with AES-256-GCM and a per-secret key derived with HKDF-SHA256. Clor decrypts a credential only to deliver it to an authorized space.
Become extraordinarily productive
Local runners are free. Add hosted runners whenever you want more power.
Already have an account? Sign in
By continuing, you agree to our Terms of Service and Privacy Policy.