KeelenUse case — OpenAI Codex
Codex comes with your ChatGPT plan. Use a configured workflow.
Use your existing Codex or ChatGPT subscription, or an OpenAI API key, for a connected project. Keelen turns Requests into planned tasks, implements changes in isolated runs, and returns pull requests or decisions for review. The roadmap can continue under the project's capacity and settings.
Choose Claude Code, Codex, GLM, Kimi, or Grok per project using your own supported subscription or API key. Switching engines preserves your roadmap. The Operator plan is $79/month: 1,000 iterations, 10 projects, 5 concurrent runs, and 5 scheduled projects on the 24/7 loop.
- Connect once with a Codex login — the loop runs on the ChatGPT subscription you already pay for.
- A standing process, not prompt-and-wait: it picks its own next task from your roadmap and keeps going.
- When configured, controls can include red-first proof, adversarial review, a verified clean-checkout command, required checks, and a review window before gated auto-merge.
- Choose Claude Code, Codex, GLM, Kimi, or Grok for each project on your own connected credentials.
Use the subscription you already have
Connect a supported Codex subscription or API key, then start with a bounded Request and inspect its acceptance criteria, branch, and review settings. Provider allowances and billing remain with the provider plan.
Request-to-roadmap progression
Keelen maintains Requests and a roadmap, so eligible work can continue under the project's settings. Other agent products may also provide background or planning workflows; compare the actual provider configuration rather than assuming a prompt-only category.
Review and merge controls
A separate adversarial reviewer examines the diff. Red-first proof and a clean-checkout test run require a verified project test command. Gated auto-merge requires the configured repository checks and a review window. Choose manual merge to keep the final click, or branch-only delivery to work without a pull request.
Honest limits
Ambiguity comes back as a question, not a guess: unclear requests raise one plain-English card in your Needs-you queue. Autonomy is bounded by your test suite — a repo without tests onboards in an honest no-test posture until the loop's own PRs add one. And provider limits are handled like weather: runs back off and retry on a budget, and those retries never count against your iterations.
Recommended plan
Operator — $79 / month
FAQ
Do I need an OpenAI API key, or does my ChatGPT subscription work?
Either works. The recommended default is a Codex login from your ChatGPT subscription — run codex login and upload the resulting auth file, and the loop runs with no per-token API charges. An OpenAI API key works too; usage then bills to your API account at cost.
Which model does Keelen use for Codex projects?
Projects on the Codex engine use the configured model through the Codex agent. Engines are chosen per project, so a Codex project can sit next to Claude Code, GLM, Kimi, and Grok projects in the same workspace — each on its own credential, each billing to its own provider at cost.
Will Keelen eat my ChatGPT usage limits?
It uses the capacity you choose to give it: concurrent runs are capped by your Keelen tier, scheduling is per project, and you can pause a project or your whole account at any time. When OpenAI reports a usage limit mid-run, the loop backs off and retries on a budget — those retries never count against your iterations.
Is Keelen Codex-only?
No. Connect Claude Code, Codex, GLM, Kimi, or Grok on your own supported subscription or API key. Grok accepts a SuperGrok sign in or xAI API key. Pick an engine per project and switch without losing your roadmap or history.