KeelenFor developers and teams with a defined backlog
Your developers sign off. Your backlog keeps moving.
Updated 2 October 2026
Keelen is an autonomous AI coding agent. It works through a standing backlog on your GitHub repo while your team is offline. Queue defined requests for nights, weekends or holidays. Connect your AI credentials. Choose how the project approves and merges work. The loop plans tasks, makes changes and reports pull requests and decisions for your team to review.
Start with one small task in a repo you understand. Choose manual merge. Progress needs an active project, work that is ready, free capacity and provider limits. A task may wait for an answer, for access or for a failed check to be fixed. Keelen does not promise a fixed amount of work by morning.
The loop picks the next eligible task from your standing roadmap. You do not need to start each task with a new prompt.
A Friday to Monday handoff
This is an example workflow, not a measured result.
Before you sign off, pick a small fix or a test improvement. Write what the change must do, answer open questions and set manual merge.
While you are away, Keelen works on the tasks you left. Each task goes through the project's build and review steps.
When you return, inspect the diff, passed and failed checks, any skipped verification and the decisions that still need you. Merge only the changes you accept.
What to put in the queue
Start with a bug you can reproduce, a missing test, a small cleanup or a small feature with a clear result. Keep open design work and unclear product calls with the people who hold that context. Queue only the work your team can review in time.
You submit the work as a Request. Keelen turns the top roadmap item into tasks with clear criteria. You can compare each one with the resulting change.
Choose what can happen while you are away
Plan approval holds work until you approve the plan. Manual merge leaves the merge call with you. Gated auto merge can land changes after the checks you set and the review window. Branch only mode pushes a branch with no pull request. These are project settings. Leaving work running outside your hours does not create a calendar or holiday schedule.
Checks and review before a change lands
If the project has a test command, Keelen checks that new tests fail without the change. They must also pass on a clean checkout. A separate review run adds evidence. So do your required CI checks and the review window. The reviewer does not have to be a different model. Look at the real result, including failures and skipped checks. A pull request is one step. It does not prove the acceptance criteria are met.
My agent stopped overnight. It was stuck on a permission prompt or a usage limit. How do I keep it running?
Your approval settings still apply. Plan review is a separate opt in. When it is on, a human approves the plan before any code is written. With manual merge, Keelen opens the PR and you click merge. A real dead end can become a plain English decision card and pause the project.
When a provider limit has a reset time
Keelen can pause for a recognized timed session or usage limit. It uses the provider reset time when it can parse one. Work becomes eligible to resume when the pause ends. Reset handling varies by engine.
Some replies give no usable reset time. Those use a bounded retry wait. That wait can grow after more usage limit failures. A retry deadline is not proof of the provider's real reset.
When a second engine can take over
A second engine can take over while the main one cools down. It must be configured and connected. Its credential must be usable. It must have no live cooldown of its own. Other scheduling controls and decisions still apply.
This does not bypass provider limits. It does not lower the provider bill. It does not promise work will not stop. It does not promise a set amount of output overnight.
An optional daily or weekly email
The progress digest email is off by default. You can opt in to a daily or weekly email. It covers merged work and open PRs. It also covers paused or blocked work and decisions that need you. The email reports progress. It does not promise completed work or resolve decisions for you.
Include internal tools and selected review findings
Your backlog can hold your own internal tools. It can also hold code fixes picked from Security, Legal and Controls reviews. Scans run apart from development. Your agent or scheduler can start repeat scans through MCP. You decide which findings become work requests.
How it works
Choose one bounded task
Write its expected behavior and acceptance criteria.
Connect the project
Connect the repository and a supported AI provider.
Set your controls
Choose manual merge for the first run and complete any required plan approval.
Review when you return
Inspect the result and decisions before accepting a change.
Not for you if
- The work needs product or design calls that you have not made yet.
- Your team has no capacity to review the results.
- You need a promise that work finishes by a deadline, or a person on call who owns it.
Hand over one task before you sign off.
Choose manual merge, describe a small change and inspect the result when you return.
Flat tiers from $29 a month plus your own coding model usage, no markup on tokens. Keelen pays for chat. 14 day trial, no card.