Kora runs Claude Code, Codex, OpenCode and Antigravity as one orchestrated team. Every agent reads from one local graph of your code, so it starts out knowing where things are and who calls them.
8–9×
With an OpenCode lead and Stretch on, every slice a free model can do goes to a free worker, and paid models are kept for the reasoning. A long run of commands stops re-reading a 150k-token context on every call.
Measured on our own long-running tasks.
Describe the work once. The lead plans it on the graph: the files to touch, the callers that change, the command that proves a slice is done.
It proposes one worker per slice: which agent, which model, how much effort, and why. You approve or change every row.
Each worker is a real agent CLI in its own git worktree, in a live pane. Type into any of them; the lead sees what you said.
Before a branch lands, a graph-verified gate catches what git would merge cleanly but breaks: a function one worker renamed and another still calls.
Claude CodeLead or worker
CodexLead or worker
OpenCodeLead or worker
AntigravityLead or workerEach agent signs in with its own login. Kora uses the subscriptions you already have and never sees your credentials.
70%
The lead asks the graph where a symbol lives, who calls it and what an edit touches, in one step each, instead of opening files until it finds out.
Measured on our own planning tasks.
Edit sites, the callers of anything whose contract changes, and what an edit touches, before a single worker starts. A cheap worker gets a slice, not a search.
kora graph explore "rate limiter"kora graph neighbours rateLimit --direction inkora graph blast_radius --file src/routes.ts
A code-shaped prompt gets the matching declarations put in front of the agent before it searches, so less of its context window goes to finding things.
> where is the token bucket refilled? + injected bucket.ts:42 refill(key, now)+ injected routes.ts:18 rateLimit(opts)
Two branches that touch different lines can still break each other. The gate reads the graph across worktrees, names the pairs that collide and suggests an order.
kora_merge_verify [limiter, routes, tests]! collide routes calls rateLimit(opts, key)→ order limiter, routes, tests
Go deeperBenchmarks against CodeGraph, GitNexus and GraphifyResearch papersThe graph on its own, in Claude CodeLearn how code graphs work
There is no Kora login. You sign in to your agents, not to us.
Your code, chats and graph stay in ~/.kora and ~/.koragraph.
No analytics of any kind. Agents talk to their own providers, exactly as they would without Kora.
Download Kora-arm64.dmg and drag Kora to Applications. It is signed, notarized and updates itself.
Sign in to the agents you use. Claude is one click; Codex, OpenCode and Antigravity use their own logins.
Open a project folder and index it from the chip next to its name. That turns on the graph.
Or build it from source
git clone https://github.com/Koragraph/Kora.git cd Kora && pnpm install # Node 24, pnpm 11, Xcode CLT pnpm build && pnpm start
Swarm workers on free models send the task they are given to that free provider. The first-run setup says so before you turn it on.