continuous-claude

Open-source orchestrator that runs Claude Code or Codex in a continuous loop — creating PRs, waiting for checks, and merging — with budget, time, and iteration caps.

Visit source

Use casesWorktree toolsPR automationGitHub Actions

Reviewed 2026-07-21

Community project documentation

Primary source reviewed

Source type: open-source. License: MIT. The linked source supports the visible capability notes but does not prove production suitability.

Open evidence source

Inference or recommendation

Verify before production

Confirm current maintenance, permissions, data handling, license obligations, failure behavior, and a human approval gate in your own environment.

Key capabilities

Caps: --max-runs (0 = infinite), --max-cost (USD), --max-duration (e.g. 2h)

Reviewer pass with --review-prompt and a separate --review-provider

Parallel git worktrees: --worktree, --worktree-base-dir, --cleanup-worktree

Early stop via --completion-signal / --completion-threshold; --stall-threshold on repeated failures

Rate control: --max-calls-per-hour; merge via --merge-strategy (squash/merge/rebase)

Practical fit

continuous-claude fits repository workflows that genuinely require repeated coding, review, CI observation, and another pass. Its built-in caps and worktree options make it more deliberate than an unbounded shell loop, but the configuration still determines whether it is safe.

The strongest use case is a narrow pull-request loop with visible progress and a separate reviewer. It is a poor fit when the objective is vague or the repository cannot tolerate automated writes.

How to evaluate it

Which max-runs, max-cost, max-duration, and stall settings will be mandatory?

Is the review provider independent and read-only?

Does the merge strategy stop for a person before changing the protected branch?

Example decision

Run a CI repair in a temporary worktree with three attempts, a small cost cap, and a separate review prompt. Let the loop prepare a mergeable PR, then stop before merge for a human decision.

Verify before you adopt it

Check current flags and defaults in the repository README.

Test completion and stall signals on a disposable branch.

Review GitHub permissions and disable automatic merge during evaluation.

Source review note

We reviewed the primary source on July 21, 2026. Product behavior, pricing, licenses, and maintenance status can change, so check the linked source before adopting it.

Best for

PR babysitting and CI repair

Long multi-iteration coding loops

Parallel work via git worktrees

Not for

Auto-merge without human review

Non-GitHub forges (GitHub PR automation only)

Risk notes

Supports infinite loops (--max-runs 0) — always set --max-cost, --max-duration, or --max-runs.

Repository permissions and auto-merge behaviors require strong safety gates and human approval before merge.

This is a community project. Verify maturity, licensing, permissions, and safety behavior before relying on it in production.