KeelenUse case · Kimi
Use a Kimi credential for reviewable roadmap work.
Connect a Kimi Code membership key or a Moonshot API key. Then a connected project can turn Requests into planned tasks. It builds the changes in isolated runs. You get reviewable pull requests and the decisions that need you. Your project capacity and controls still apply. Kimi or Moonshot bills you on their own plan.
Connect each engine with its own key. Kimi takes a Kimi Code membership key or a Moonshot API key. Claude Code takes a Claude subscription or API key. Codex takes a ChatGPT sign in or an OpenAI API key. GLM takes a Z.ai key. Grok takes a SuperGrok sign in or an xAI API key. You choose the engine for each project. The Indie plan is $29/month: 200 iterations, 3 projects, 2 concurrent runs, and one scheduled project on the 24/7 loop.
- Connect your Kimi key so Kimi can progress your roadmap on GitHub.
- Pick a supported Kimi key setup that fits your provider's terms. Kimi sets the billing and the limits. Your Keelen plan does not change them.
- Your project controls can add more checks, such as a second review of the diff, a clean checkout command, and required checks. You can also require a manual merge or a review window. Red first proof then needs a verified test command.
- You can move a project between Kimi, Claude Code, Codex, GLM, and Grok. The roadmap stays.
The membership engine
Use a supported Kimi Code membership key for its included allowance. Use a Moonshot API key for metered use. Requests become roadmap items. Each item becomes a task with acceptance criteria. Each task runs on its own under your project controls. Start with a defined maintenance task. Check the current limits and charges on your provider's plan.
Evidence you can check
A second review reads the diff on its own. It does not see the talk that built the change. A verified test command for the project turns on red first proof. It also runs the tests on a clean checkout. Gated auto-merge needs the repo checks you set and a review window. Read the results, including the failures and the missing evidence, before you accept the change.
A night on the loop
The scheduler picks your top task. It boots an isolated VM, clones the repo, and works the task on Kimi through Claude Code. A verified test command gives test evidence before and after the work. Work follows your PR or branch policy. Decisions that need you come back with the task's acceptance criteria. Check the actual progress and the remaining decisions when you return.
Honest limits
Runs handle provider weather for you. When Kimi reports a usage limit or an overload window, runs back off and retry on a budget. Retries never count against your iterations. The loop starts again on its own. Ambiguous requests become questions rather than guesses. Your test suite also bounds the autonomy. A repo with no tests onboards in an honest no test posture. It stays that way until the loop's own PRs add a test.
Recommended plan
Indie: $29 / month
FAQ
What Kimi credential does Keelen need?
One of two keys, pasted once. The recommended key is a Kimi Code membership key from kimi.com. The loop then runs on your flat coding quota with no charges per token. A Moonshot Open Platform API key works too. Usage then bills per token to your Moonshot account. Either way the key is encrypted at rest. It is injected only into the single use VM that runs your iteration, and deleted the moment you revoke it.
Is Kimi good enough to run unattended?
Try Kimi on your repo. Look at the checks it can really run. Keelen adds a second review of the diff, and a verified test command gives red first and clean checkout evidence. Your required checks and merge policy decide when work can land. Keep a human review for calls the evidence cannot settle.
Is Keelen Kimi-only?
No. Connect Claude Code, Codex, GLM, Kimi, or Grok with your own supported subscription or API key. Engines are per project: run Kimi on the side project and Claude Code on the client repo, side by side in one workspace.
What does Keelen cost on top of my Kimi plan?
A flat platform fee with zero token markup. Indie is $29/month for 200 iterations. Operator is $79/month for 1,000. Agency is $299/month for 5,000. Your Kimi Code membership key keeps usage on the membership quota. A Moonshot API key bills to Moonshot under that provider's terms. Iteration and pull request counts vary with the repo and the request.