Repository navigation
FAQ
Questions people have asked about Even Keel, with the answers. Setup and every option are in the user guide; this page is the short version of the "but why" and "but what about".
The numbers here are from my own chain over three weeks (2026-09-28 to 2026-10-18, one user, mostly Opus), read from the session transcripts by the built-in statistics. The SQL behind each of them is in docs/posts/sequential-by-design.sql. Dollar figures are API-equivalent token prices, not what a subscription costs.
On a subscription the budget is the weekly usage window, and ten agents don't make it bigger, they empty it sooner. Backlog tasks are connected, so the agent on task B should read A's merged code instead of guessing what A will look like. And questions, reviews and merges are your attention, which doesn't scale to ten queues. Different projects are different repositories, so their chains do run side by side.
The long version: Ten agents at once is the wrong unit.
Partly. A handoff roughly halves the reading. A fresh session reads about 80k tokens of context before its first edit, a continuation after a handoff about 40k; the median spend to the first edit is $1.51 against $0.74 (Opus, 371 fresh sessions and 318 continuations). The note tells the new session what is done, what is left and where to look, so it skips the exploring. It still re-reads the files it is about to edit.
Not measured yet: a handoff against the CLI's own auto-compaction. That experiment is running; its results go into the next post.
No. A project runs on one account per provider, and when its limit is spent the chain waits for the reset; it never switches to another account to keep going. Several accounts exist so that separate projects can spend separate subscriptions (a side project does not eat the main one's window), and for API keys.
Sessions run through the unmodified claude and codex CLIs on accounts you sign in with yourself, under Anthropic's and OpenAI's terms. OpenAI's terms rule out getting round its limits, so Even Keel refuses a second Codex account on the free plan. It does not share, pool or resell access. The terms that apply: Before you run it.
The chain waits for the reset. If the prompt cache is still warm by then, the same session is resumed; otherwise a fresh session continues from a handoff note in the same worktree. Only that project waits; a project on another account goes on.
Only that task waits. You answer in the page's chat, as a comment in the tracker or in Claude's Remote Control from your phone. Over the three weeks, 13 % of chain task time was waiting for me, and four in five tasks never waited at all. For nights there is unattended mode: sessions ask nothing, and a task that needs an answer is parked with the question as a tracker comment.
By default, yes: the session does the task and merges its branch, and Even Keel closes the task and starts the next one. The control is in how you write the task and in your project's rules, CI and check commands: the next task waits for the CI's verdict on the main branch, and a red one is fixed first. If you want to review each change, turn on pull request mode (experimental): Even Keel opens a pull request on GitHub or Forgejo instead of merging, and review feedback goes back to the task's session.
Sessions run without asking on each tool call (--permission-mode auto for Claude), so set up the permissions and hooks you want in your Claude Code settings before you start a chain.
It depends on undocumented behaviour of the CLI: background sessions, session files, the transcript format. So chain sessions do not run on whatever version your CLI updated itself to: Even Keel downloads the version it was last checked against and runs them on that, while your own claude keeps updating. A new version becomes the checked one only after a live run through the launch, a question, the answer, a handoff and a stop. That moves the fragility rather than removing it; if something breaks, please open an issue.
Trackers: Huly, GitHub Issues and Linear. Agents: Claude Code, and Codex for projects or tasks set to it. CI: GitHub Actions and Forgejo. It runs as a service on Windows (daily use) and Linux (checked end to end); macOS is expected to work but has not been checked. Behaviour never checked live is listed in What has not been verified.
No. Everything runs on your machine; sessions talk only to the providers you signed in with. Even Keel reads only the expiry dates from Claude's credentials and the e-mail and plan from Codex's; tokens are never copied or sent anywhere. Keys of plugins and MCP servers stay in Even Keel's .env behind a local gateway and are kept out of the sessions' environment.