Turn a GitHub issue into a PR with Claude Code.

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 implementation. Keelen adds a managed roadmap for work you are ready to hand over. It plans your requests, selects the next eligible task, and keeps steering rules across runs. You can reorder the work and answer the planner's questions.

The reason to try Keelen is that combination of planning, execution and review controls. Background execution is also available in Claude Code itself. Start with one change to decide whether Keelen's workflow earns a place alongside it.

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 as merged with four checks passed. This recording shows Keelen merging; the first workflow below leaves that decision with you.

That is a visible result, but the recording does not give you a linked PR diff and full check output to inspect against the original request. That complete public walkthrough is still missing. Judge your own first result by reading the changes and checks with manual merge selected.

50 seconds, unstaged

GitHub Actions may already cover your task

Claude Code's official GitHub Action can work from issue comments and run saved prompts on GitHub events or schedules. It is a direct option when your work already lives in issues and you want to own the workflow configuration. Follow its setup guide for repository access, authentication and PR creation behavior.

Claude Code GitHub Actions documentation →

Cloud routines can run while your laptop is closed

Claude Code routines run saved prompts on Anthropic's cloud infrastructure, with scheduled, API or GitHub triggers. If a recurring prompt covers your work, consider that option. Keelen is worth evaluating when you want to manage the work as a roadmap with tasks, acceptance criteria and surfaced blockers. Native options checked 5 September 2026.

Claude Code routines documentation →

Give the first request a clear finish

Include the behavior you see, how to reproduce it, and what should happen instead. Name the relevant screen or endpoint and ask for a regression test using the repository's existing suite. Keep the scope small enough that you can judge the diff.

Before calling it useful, check that the PR addresses the request's acceptance criteria, that its checks actually ran, and that you would accept the change. A created branch or an opened PR alone does not establish any of those outcomes.

Read the checks before you merge

Keelen runs a separate review of the diff without the implementation run's conversation context. It runs verification according to the project's test setup. Where the failing test check applies, new tests must fail without the implementation and pass with it. Your configuration determines which checks run; failed or skipped verification needs 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 Needs you for questions or blockers. A request can need clarification, a working engine connection or a setup fix before development starts. You can pause the project at any time. Manual merge leaves merge conflicts and the final merge decision with you; it does not include the automatic merge and conflict recovery path.

The work runs in Keelen's single use VMs. Read the security model before granting repository access or connecting Claude.

The full security model →