KeelenFor people who run Codex and have more issues than prompts
Give Codex the whole backlog.
Updated 3 September 2026
Keelen holds a roadmap for your GitHub repository and works it with Codex on your own key. You write requests in plain English. A planning pass turns each one into tasks with acceptance criteria. The loop picks the top task, implements it in a single use VM, opens a pull request, and picks the next one. You reorder priorities and answer its questions. You do not hand it tasks one at a time.
One prompt, one task, versus a roadmap
A per task coding agent's designed workflow is a dispatch: you hand it a task, it works, you review, you hand it the next one. That fits one off work. It breaks down when the real job is a backlog, because someone still has to decide what is next, write it up, and feed the machine every morning.
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
New tests are applied without the implementation and must fail; tests born green are rejected. An independent review of the diff by a model with no context from the run. Your own suite on a clean checkout. No merge over a red required CI check. A review window before gated auto merge, or manual merge, or branch only, per project. The loop may not weaken a check to get to green.
The same loop, any of four engines
The engine is a per project setting. Codex here; Claude via Claude Code, GLM 5.3, or Kimi K3 on another project in the same workspace, each on its own key, each billing to its own provider at cost. Keelen adds no markup on tokens.
Numbers you can read
Per project loop metrics: cycle time per task, verification pass rate, answer latency on the questions it asks you, and token burn.
If it breaks
Failures are classified into 30 kinds. Infrastructure failures and provider quota failures never count against your work. A real dead end becomes one plain English decision card and the project pauses instead of burning quota.
How it works
Install the GitHub App
On the repository.
Connect your Codex key
One per project.
Write the requests
The first pull request typically lands within minutes.
Set the merge policy per project
Gated auto merge, manual merge, or branch only.
Not for you if
- You have one task, not a backlog. A per task agent is the better tool for that, and faster to start.
- You want to watch it work. Keelen has no editor and no chat panel. It works from the roadmap and reports back as pull requests.
- Your repo has no tests and you will not add any.
- You need product judgement. Keelen executes and verifies. It does not decide what your product should be.
Write the backlog once
Flat tiers from $29 a month plus your own model usage, no markup on tokens. 14 day trial, no card.