KeelenUse case — Claude Max
Use your Claude plan for reviewable roadmap work.
Use your existing Claude Pro or Max subscription, or an Anthropic 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.
Keelen also runs on other AI accounts. Connect a Claude Pro or Max login (or Anthropic API key), a Codex login from your ChatGPT subscription (or OpenAI API key), a GLM (Z.ai) API key, a Kimi Code membership key or Moonshot API key, or a SuperGrok sign in or xAI API key for Grok. Choose an engine per project. The Operator plan is $79/month: 1,000 iterations, 10 projects, 5 concurrent runs, and 5 scheduled projects on the 24/7 loop.
- Keelen uses the connected provider credential; provider billing and allowances remain terms of that plan, separate from Keelen's platform tier.
- Wake up to tested pull requests with acceptance criteria, not a chat transcript to replay.
- Configured controls can include red-first proof, adversarial review, clean-checkout tests, required checks, and a review window; test evidence requires a verified project command.
- Switch a project between Claude Code, Codex, GLM, Kimi, and Grok while keeping its roadmap.
Use the subscription you already have
Connect a supported Claude subscription or API key, then start with a bounded Request and inspect its acceptance criteria. Keelen's platform tier is separate from the provider plan; provider allowances and billing remain with that provider.
What a night on the loop looks like
The scheduler picks the top task from your roadmap, boots a fresh single-use VM, clones your repo, and works the task with Claude Code. A verified test command enables failing-test proof and a clean-checkout test run. Work returns through your selected PR or branch policy, with acceptance criteria and review evidence. When a decision needs you, the loop raises it for review. Other eligible work can continue within the project's capacity and controls.
Controls depend on the project configuration
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
Keelen asks instead of guessing: ambiguous requests come back as clarifying questions, not creative interpretations. Your test suite is the ceiling on autonomy — a repo with no tests onboards with an honest no-test posture until the loop's own PRs add a suite. And your plan's limits are respected: when Claude reports a usage window, runs back off and retry on a budget, and those retries never count against your iterations.
Recommended plan
Operator — $79 / month
FAQ
Will Keelen burn through my Claude Max usage limits?
It uses whatever capacity you choose to give it, and you hold the dials: concurrent runs are capped by your plan tier, scheduling is per project, and you can pause one project or everything at any time. If Claude reports a usage limit mid-run, the loop backs off and retries on a budget — those retries never count against your Keelen iterations.
Does Keelen see or store my Claude credentials?
Your token is encrypted at rest under independently rotated keys and injected only into the isolated single-use VM that runs your iteration — the machine is destroyed when the run ends, and credentials on disk die with it. Revoke access anytime and the token is deleted immediately. Keelen never resells tokens; usage bills to your own Anthropic account.
Do I connect a Claude subscription login or an API key?
Either. The recommended default is a subscription token minted with Claude Code's setup-token command — the loop then runs on your Claude Pro or Max plan with no per-token API charges. An Anthropic API key works too; usage then bills to your API account at cost.
Is Keelen Claude-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.