Koydo Command Center
What KCC isIsolated by default
Every agent works in its own git worktree and branch, so parallel agents never overwrite each other. You review and merge each one on your own command.
Loading…
Koydo Command Center
Run a whole team of AI coding agents from one terminal.
KCC is a terminal-native, headless orchestrator for AI coding agents. Launch many agents in parallel — each isolated in its own git worktree, on its own account — and drive them all from a single command line. No GUI, no lock-in. Free and open source under the MIT license.
MIT licensedmacOSLinuxWindowsNode 20+
What KCC is
One terminal, many agents.
You already use terminal coding agents. KCC lets you run many of them at once and keep them from stepping on each other — then gives you one place to watch, steer, and merge their work.
Its own account, its own headroom
Pin each pane to its own login so agents don’t fight over one rate limit. KCC routes work to whichever account has room to spare.
Terminal-native and headless
Everything is a command. Drive it by hand in a rich full-screen workspace, or script it end-to-end for CI and automation with clean JSON output.
Yours to read and change
KCC is open source under the MIT license. Read the code, fork it, extend it, and open the commands you want.
Install
InstallInstall KCC
You need Node.js 20 or newer. KCC installs as two interchangeable commands, kcc and koydo.
Install with npm
npm install -g koydo-command-centerOr install from source
On macOS and Linux you can also run the guided installer: bash ./scripts/install.sh (or scripts/install.ps1 on Windows).
git clone https://github.com/Koydo/kcc-cli
cd kcc-cli
npm install
npm linkCheck it works
kcc --versionmacOS tip
On macOS, /usr/bin/kcc belongs to the system Kerberos tools and can shadow KCC in cron jobs and non-login shells. Use the identical koydo command there — same CLI, same flags.
More install channels — coming soon
Homebrew, Scoop, and Winget packages are on the way. For now, npm and installing from source are the quickest paths.
Quickstart
Your first run
From a fresh install to agents doing work, in four steps.
1. Set up a starter workspace
Create a clean, generic setup
Two isolated agent workspaces for this machine, with no accounts or paths assumed. kcc doctor confirms your environment is ready.
kcc init --starter
kcc doctor2. Open the atelier
Run KCC with no arguments
Opens the atelier — a full-screen terminal workspace with panes, tabs, and a “:” command palette.
kcc3. Launch your agents
Bring your agents up in tiled panes
Prefer to open specific agents directly? Use kcc launch.
kcc run4. Give them work
Message an agent, or hand off a whole task
kcc talk "run the tests and report back"
kcc ship "add a health check route"Key features
Key featuresBuilt to run a fleet, safely.
The atelier workspace
Run KCC with no arguments to open the atelier — a full-screen home for your agents. Split it into panes, flip between tabs, and run any command from a fuzzy “:” palette. No mouse required.
An account per pane
Sign in to several Claude, Codex, or Gemini accounts at once and pin each to its own pane, so parallel agents never share one rate limit. KCC tracks each account’s headroom and swaps a slot to a fresh one when it runs low.
Talk to your agents
Message one agent, a group, or the whole fleet in plain English with kcc talk. Replies come back to you, correlated to who said what — no guessing which pane answered.
Plan first, then execute
Ask for a plan and KCC prints it and waits at an approval gate. Nothing runs until you say go — so you stay in control of anything that touches your repo.
Checkpoints and rewind
KCC snapshots your files before every write. If an agent goes the wrong way, rewind the change — files, context, or both — and pick up from a known-good point.
Cost dashboard
See token and estimated-dollar spend by account, session, repo, and model — today versus this week, with the top spenders called out, so a long run never surprises you.
Reach it from anywhere
Put KCC on your private Tailscale network, drive it from your phone with a mobile control screen, or send commands from Telegram, Signal, or WhatsApp.
MCP in both directions
Expose KCC as a Model Context Protocol server for your other tools, and let your agents reach for MCP tools themselves — one setting, both ways.
Memory that survives restarts
Agents keep durable, cross-session memory and searchable transcripts. After a crash, “what happened at 3am” is still an answerable question.
Ship it — or race it
Send one task the whole way with kcc ship: do it, commit, branch, push, open a PR, watch CI, self-fix. Or run a tournament where several agents attempt the same task and the best diff wins.
Command reference
Every command, one line each.
Run kcc <command> --help for the full options on any of these.
Set up & launch
kcc init- Detect your tools, write a config, and set up folders. Add --starter for a clean, generic setup with no accounts or paths assumed.
kcc doctor- Check your environment, config, and terminals. --fix applies the safe repairs for you.
kcc run- Initialize, sync, and launch your agents in one step.
kcc launch- Open your agents in terminal panes.
kcc mux- KOYDOMUX — KCC’s own terminal multiplexer that owns panes natively, so you don’t need tmux.
Drive your agents
kcc talk- Message a running agent, a group, or the whole fleet in plain English.
kcc do- Describe a task and KCC routes it to the right specialists and runs it.
kcc route- Preview which specialists a task would use, before you run it.
kcc agent- Run KCC’s autonomous coding agent on a single task.
kcc ship- Take a task all the way: do it, commit, branch, push, open a PR, watch CI, self-fix.
kcc plan- Produce a plan and stop at an approval gate — it never executes on its own.
kcc fanout- Run several agents on the same task in parallel worktrees, then merge the winning diff.
kcc orch- Drive other panes: send, broadcast, read, spawn, and listen.
kcc watch- Watch the repo and keep an agent’s memory fresh as files change.
Review & control
kcc review- Review agent work: per-slot diff summaries, full diffs, and inline comments.
kcc board- A kanban board over your tasks and decisions: pending, ready, active, blocked, done.
kcc gate- Approve or answer an agent’s decision from your terminal or a chat app.
kcc checkpoint- Inspect and manage the file snapshots taken before every write.
kcc rewind- Restore to a checkpoint — files, context, or both.
kcc roster- See every agent at a glance: name, tool, state, and what it’s running.
kcc logs- Search and tail durable pane transcripts that survive restarts.
kcc ask- Ask what your agents are doing; KCC answers from their live output.
Accounts, cost & memory
kcc cost- Token and estimated-dollar spend by account, session, repo, and model.
kcc memory- Store and recall notes and handoffs across sessions.
kcc why- Answer a question from learned memory, with citations.
kcc session- Manage your agent sessions and keep tokens healthy.
kcc worktree- Manage the isolated git worktree behind each agent.
kcc verify- Run a repo’s own checks — tests, lint, typecheck — before you ship.
Connect & extend
kcc mcp- Expose KCC as an MCP server and let agents use MCP tools.
kcc net- Put KCC on your private Tailscale network for remote control.
kcc workers- Run KCC work on other machines over SSH or the relay.
kcc remote- Drive KCC from your phone with a mobile control screen.
kcc relay- Control the fleet from chat — Telegram, WhatsApp, and more.
kcc hooks- Inspect, dry-run, and validate lifecycle hooks.
kcc notify- Desktop and chat notifications for agent events.
Open source, MIT licensed.
Read the code, open an issue, or contribute. KCC is built in the open — the same tool the Koydo team runs every day.
