One terminal. Your coding agents.
Bring your Claude, Codex, and Devin accounts into one local workspace. Choose a model, work on your project, and keep your sessions and usage in view.
Open source · local workspace · native source preview
Run the tests. Fix the failure. Show me the diff.
- 01Inspect the projectRead files and find the relevant test.read
- 02Test, repair, test againRun prepared dependencies in the isolated Linux runner.run
- 03Review what changedKeep the diff and session history close to the work.review
Less switching. More making.
One place to choose an account, open a project, and get back to the work.
Your accounts, together.
Name your accounts and select the model you want. Keep credentials separate while using a familiar workflow across supported providers.
Context you can come back to.
Save sessions locally. Resume the project, inspect earlier work, and decide what happens next from the same terminal.
Usage with an honest answer.
See observed usage and known quota windows. Exhausted Claude accounts wait for their reported reset. Unknown usage stays unknown.
From a failing test to a change you can review.
Read, edit, and test with workspace tools. Keep the result close enough to inspect.
Commands run offline with prepared public dependencies. Native macOS tools and Git writes remain outside this runner.
Set up workspace commands ↗A terminal that feels like yours.
Choose a focused pane, edit its layout, or generate a new one. Keep the working view while you try something different.
Your presentation can change without rebuilding the app. A layout cannot grant access to credentials or turn on executable hooks.
Panes, sessions, and extensions ↗Choose the right layer for your work.
Coding assistants, cloud agents, and orchestration frameworks solve different problems. xcb focuses on your local coding workspace.
Work inside one provider
A provider CLI gives you its native experience and newest provider-specific capabilities.
Delegate or build workflows
Cloud agents take work into remote environments. Orchestration frameworks help you build coordinated agent applications.
Bring your workspace together
xcb puts supported accounts, model choice, local history, and usage behind one terminal interface.
Useful today. Clear about the edges.
Native xcb is a source preview. The current evidence covers specific builds and tested accounts, not every provider or machine.
Claude & Codex
Installed coding workflows passed on macOS ARM64: failing test, repair, passing test, and Git inspection.
Supported builds and setup ↗Devin
Authentication and model discovery passed. The tested account hit provider quota before a coding turn.
Current Devin boundary ↗Tests & builds
Offline Linux ARM64 commands, prepared public dependencies, and read-only Git inspection. No native macOS command execution.
What the runner supports ↗Make room for better work.
Start with the native source build. You’ll need Git, Rust 1.97.1, platform build tools, and a supported provider setup.
git clone https://github.com/hraness/xcb.git
cd xcb
rustup toolchain install 1.97.1 --profile minimal
./scripts/install-native.sh
export PATH="$HOME/.local/bin:$PATH"
xcb update enable --policy notify
xcb --helpPackage and release details
First xcb package release in preparation
No native xcb binary or @hraness/xcb npm package is published. The historical v0.3.0 archive is AgentMixer. Check releases.
Before you begin.
What is xcb?
xcb, short for Excalibur, is an open-source terminal workspace for coding agents. It brings your provider accounts, model choices, local sessions, and usage into a common interface. The native Rust app is available as a source preview.
Is it a multi-agent orchestrator?
Its focus is the workspace around your coding agents: accounts, models, sessions, tools, and controlled continuation. It is not a hosted fleet of parallel agents or a visual workflow builder. Use a dedicated orchestrator when coordinating a task graph is your main need.
Do I still need provider accounts?
Yes. Connect your own supported provider accounts and installed runtimes. xcb does not include model access, pool unrelated subscriptions, or remove provider usage limits. Provider pricing and terms still apply.
What stays on my computer?
xcb keeps its account state, session history, configuration, and panes locally. Model requests still go to the provider you choose. There is no required xcb cloud account, and local usage measurement does not automatically publish your data.
Can I use it for daily work today?
The tested Claude and Codex setups passed real coding workflows on macOS ARM64. Native xcb is still a source preview: provider builds are restricted, command execution uses offline Linux, and the tested Devin account reached quota before a coding turn. Read the setup guide to decide whether those boundaries fit your projects.
What does it cost?
xcb is MIT licensed and free to build from source. Your provider subscriptions, model usage, and any services you choose are separate. There is no xcb subscription required to use the local workspace.
Your accounts. Your workflow.
A local workspace for developers who work with more than one coding agent.
xcb / Excalibur · Built by Hraness · MIT licensed