The control plane
for coding agents.
Run Claude Code, Codex, Cursor, Gemini and seven more from one surface — one at a time, or as a team on one goal. Bring your own subscription.
curl -fsSL https://dl.ycodium.com/install.sh | shRemote is the default, not an afterthought.
Ycodium runs on a machine you own — a spare desktop, a home server, a small cloud box — and every client connects to that one place.
- Multiple clients connect to the same environment at once.
- Close your laptop — the agent keeps running.
- Check progress from your phone.
- Switch devices and pick up the same thread.
Straight to the Host over your LAN or a reachable address. No third party in the path.
No open ports. Ycodium's relay — hosted or self-hosted — forwards the connection between your client and the Host.
Already on a tailnet? Publish the Host over Tailscale Serve HTTPS and pair through a clean MagicDNS URL.
Point the desktop app at user@host. It starts or reuses Ycodium there and forwards a local port — nothing to set up by hand on the remote box.
Bring your own sub
Ycodium doesn't resell tokens. Plug in the agents you already pay for with the credentials you already have — eleven come set up by name, and anything that speaks ACP is one command away.
One goal, a team of agents.
Define a team once — the roles, the model each one runs, who hands off to whom. After that you give it a goal in plain words. Every role gets its own thread, its own checkout when it needs one, and a board that shows where the work actually is.
- plannerDone
- implementerIn progress
- reviewerReady
- A model per role — or point the role at a routing table row
- Isolated worktrees, gathered back without a pull request
- Members message each other; the run's traffic is on the record
- Pause, resume or stop — every member thread stays where it is
A roster you reuse, like a project. A fast model drafts, a careful model reviews, and roles that would edit the same files get their own worktree. Pause, resume or stop a run from the board without leaving the conversation.
An agent can start a thread on another provider by itself, keep working, and be told when that one finishes, fails, or needs an approval. A routing table decides which model takes which kind of work.
Every turn checkpoints. Roll back, diff, or ship it.
Before an agent touches a file, Ycodium checkpoints the workspace as a hidden git ref. Pull the diff for any turn, restore an earlier checkpoint if it went sideways, and when the result is good, one button opens the PR on GitHub — title, body, and changelog generated for you.
- Automatic checkpoint on every turn — nothing to configure
- Restore any earlier checkpoint in one click
- Inline diff review before you push
- One-click PR with a generated title, body & changelog
One thread, three surfaces.
Start a thread on the web, keep it going on desktop, check in from your phone — same environment, same history, no hand-off required.
Or just say it in the group chat.
Run a bot in Telegram, WeCom or Lark and talk to your agent from the app your team already sits in. It is a way in, not a separate agent: the work lands in a normal thread on a normal project, and you can pick it up later from the web, desktop or your phone.
- @ the bot with a sentence and a turn starts on your machine
- Approvals arrive as buttons — tap one and it carries on
- Hand a whole goal to a team without opening the app
- One row per group: its own project, its own permissions
@ycodium find out why the nightly build fails, then fix it
Run the test suite before pushing?
Fixed and pushed — the lockfile had drifted after a merge.
Everything else, without leaving the thread.
The panel on the right carries the tools you would otherwise switch windows for. They follow the project you have open, and they run on the environment — not in your browser.
Stage, unstage, commit, switch branch or worktree. Publish a local repository to GitHub or GitLab and wire up the remote in one flow.
Browse, open, edit, search, upload and download — on the machine the agent works on, not a copy of it.
A real shell on that same machine, in a drawer under the conversation.
Read and review GitHub pull requests and GitLab merge requests in the panel.
A built-in preview for the dev server the agent just started.
Four settings, per thread, from the composer: ask every time, auto-accept edits, auto, or full access.
Teach it your tools once. Every agent gets them.
Add an MCP server or a skill in Settings and every provider Ycodium launches receives it. Ycodium never edits a provider's own config files — it passes the entries at launch time, so nothing you set up by hand gets overwritten.
stdio, http or sse, with per-CLI switches and a health check that runs from the environment. A CLI that cannot speak a transport is shown disabled, never silently skipped.
A folder with a SKILL.md, written where Claude, Codex and OpenCode look for it. Two switches decide whether the agent may call it and whether you may.
Environment entries apply to every project on that machine. Entries in a repository's ycodium.json travel with the repo and win on a name clash.
See what it all cost.
The Usage page reads the providers' own session history across every connected environment and puts it in one chart — API-equivalent cost, processed tokens, cache savings, and the split by provider and model.
Subscription billing is separate from the raw token cost shown here.
Your agents deserve better than a terminal.
Install it, plug in the harness you already pay for, and let your agents get to work.
curl -fsSL https://dl.ycodium.com/install.sh | sh