Give Codex the whole backlog.

A roadmap for continuing work

Coding agents can do many tasks, and some run in the background. For a continuing backlog, one question matters. Are the repo, the provider setup, the review policy, and the next item clear? If so, work can go on safely.

Keelen's unit of work is the roadmap. Steering rules and lessons persist across runs, so a correction you make once holds for the next task.

Five checks before anything merges

A verified project test command enables red first proof. It also runs a clean checkout suite. Configured required checks protect a merge. Project controls add independent review, a review window, manual merge, and branch only mode. When the guards are on and can check the change, they block detected assertion removal or weakening within their supported scope. Supported exceptions can let those changes through. A declared exception does not prove a human approved it. The guards can be turned off. Missing inputs can make them skip the check. They do not catch every way a test can lose meaning. The tests and code still need human review.

The checks in detail →

Choose an AI engine for each project

Use Codex on one project. Use Claude Code, GLM, Kimi or Grok on another, where the provider connection is supported. Connect your own subscription or API key. Each provider has its own methods. Keelen adds no markup on tokens. Provider limits and bills remain separate.

Numbers you can read

Each project shows loop metrics. You can read cycle time per task, the verification pass rate, how long it takes to answer questions, and token burn.

If it breaks

Failures fall into 30 kinds. Infrastructure failures never count against your work. Provider quota failures never count either. A real dead end becomes one decision card in plain words. The project pauses instead of burning quota.