KeelenFor solo builders with a GitHub repo and a small issue to finish
Turn a GitHub issue into a PR with Claude Code.
Updated 12 September 2026
Bring one issue from your GitHub repo to Keelen as a request. Keelen plans tasks with acceptance criteria. It runs Claude Code in its own VMs to make the changes. Choose manual merge and you get pull requests you can inspect. You review the diff and the check results, then decide what lands.
Start with a small bug or a missing test in a repo you understand. You need a Keelen account, GitHub access, and your own Claude connection. Copy the issue's description into a Request. Or turn on GitHub Issues in project Settings. It is off by default. Add your chosen label to an open issue. Keelen adds it as a Request. The app may need your consent to read or write issues. Merges need green CI and follow your project's merge policy.
After the first request, add more requests. Keelen keeps a roadmap and selects the next eligible task, so you do not start each task. Claude Code can submit your issues as Requests through Keelen's MCP server. Questions, provider limits and failed checks can stop progress.
Keep Claude Code for the work you want to drive
Use Claude Code in your terminal when you want to explore an idea or steer the work. Keelen adds a managed roadmap for the work you hand over. It plans your requests and picks the next task. It keeps your steering rules across runs. You can reorder the work and answer the planner's questions.
The reason to try Keelen is that mix of planning, execution and review controls. Claude Code can also run work in the background. Start with one change. Then judge whether Keelen's workflow earns a place next to your terminal.
What you can inspect today
The existing 50 second MCP demo shows setup from a coding agent and a recorded result. At 0:40, GitHub shows a Pomodoro timer PR merged, with four checks passed. That clip shows Keelen merging. The first workflow below leaves that call to you.
That is a real result, but the clip gives no linked PR diff or full check output to compare with your request. A full public walkthrough is still missing. Judge your own first result by reading the changes and checks with manual merge on.
Claude Code MCP setup demo · August 2026 · 50 seconds
GitHub Actions may already cover your task
Claude Code's official GitHub Action can work from issue comments. It runs saved prompts on GitHub events or schedules. It is a good fit when your work already lives in issues and you want to own the workflow setup. Follow its guide for repo access, sign in and PR creation.
Cloud routines can run while your laptop is closed
Claude Code routines run saved prompts on Anthropic's cloud. They start from a schedule, an API call or a GitHub event. If a prompt you repeat covers your work, consider that option. Try Keelen when you want a roadmap with tasks, acceptance criteria and clear blockers. Native options checked 5 September 2026.
Give the first request a clear finish
Include the behavior you see, how to reproduce it, and what should happen instead. Name the screen or endpoint. Ask for a regression test that uses the repo's own suite. Keep the scope small enough that you can judge the diff.
Before you call it useful, check that the PR meets the request's acceptance criteria. Check that its checks ran. Check that you would accept the change. A branch or an open PR on its own does not show any of that.
Read the checks before you merge
Keelen runs a separate review of the diff. That review shares no context with the run that wrote the code. It runs checks based on the project's test setup. Where the failing test check applies, new tests must fail without the change and pass with it. Your setup decides which checks run. Failed or skipped checks need your attention.
A PR can appear before verification finishes. In manual merge mode, wait for the results and review the required GitHub checks yourself. Keelen leaves merging to you. Checks catch classes of failure; they do not guarantee correct software.
Stay available for decisions
Watch the roadmap and the Needs you list for questions or blockers. A request may need an answer, a working engine link or a setup fix before work starts. You can pause the project at any time. With manual merge, you handle conflicts and the final merge call. It does not include automatic merge and conflict recovery.
The work runs in Keelen's single use VMs. Read the security model before you grant repo access or link Claude.
How it works
Create your account and open the email link
The button starts account setup. Follow the sign in link in your inbox to finish signing in.
Connect Claude, then GitHub
Connect Claude with your subscription or API key. Then install the Keelen GitHub App with repo access. Choose the existing repo to import.
Choose Open PR, I'll merge
Choose this policy during project setup. Add the issue's description as your first request. Answer any setup questions. Branch only opens no PR.
Review the first result
Wait for a PR and its check results, then compare the diff with your request. If work is blocked, read the explanation in Keelen. Setup, task scope and required decisions affect how long the result takes.
Not for you if
- You want to steer every step in the terminal. That is Claude Code by hand, and it is the right tool for that.
- You have no way to check the change and will not add tests. This first exercise assumes a repository with useful checks.
- You want every issue to start work with no label. This intake needs an open issue with the label you choose.
- You need someone to own product decisions or be on call. Keep a person responsible for the outcome.
Start with one issue you can review
Create your account and connect Claude and the repo. Then submit the request with manual merge selected.
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.