#The fix pipeline
Every issue Claudear picks up moves through a state machine:
- Pending — issue queued for processing
- Processing — AI agent actively working on a fix
- Success — pull request created
- Merged — PR merged into main
- Resolved — issue resolved (auto or manual)
- Closed — PR closed without merging (triggers retry)
- Failed — attempt failed (triggers retry with exponential backoff)
- Cannot Fix — retry budget exhausted; flagged for manual review
Review pipeline
After a PR is created, Claudear watches for code reviews and addresses feedback automatically:
- Watching PR — polling for new reviews and comments on the open PR
- Review Received — changes requested or inline comments detected
- Addressing — AI agent processes feedback and generates updated code
- Update Pushed — new commit pushed to the PR branch (returns to watching)
Ask pipeline
When the AI agent encounters a blocking question during processing, it asks a human for input:
- Question Asked — question sent to your configured notification channels
- Awaiting Reply — polling for human response (configurable timeout)
- Answered — reply received, answer incorporated into context
- Timeout — no reply received; continues with best-effort context if enabled, otherwise fails
- Continue — agent resumes processing with the new context
Regression pipeline
After a fix is merged, Claudear monitors for regressions over a 24-hour window:
- Awaiting Release — waiting for a release that includes the fix commit
- Monitoring — release detected; hourly regression checks for 24 hours
- Resolved — monitoring complete with no regression detected
- Regressed — regression detected during monitoring; triggers a new fix attempt
Cascade pipeline
When a fix is merged or released, Claudear can automatically propagate changes to downstream repositories:
- Merge / Release — upstream PR merged or new release published
- In Progress — generating cascade fix PR in downstream repository
- Completed — cascade PR created successfully
- Failed — cascade fix generation failed
- Skipped — cascade rule didn't match or depth limit exceeded
#Retries
When a fix fails or the PR is closed, Claudear retries with exponential backoff. Configure max_retries, base_delay_ms, and max_delay_ms in [retry].
# List pending retries
claudear retries list
# Process all due retries now
claudear retries process
#PR monitoring
Claudear polls PR status. When a PR merges, it auto-closes the issue if auto_resolve_on_merge = true.
# Show all tracked PRs
claudear prs list
# Continuous monitoring loop
claudear prs monitor --continuous
#AI questions
When the AI needs clarification, it sends questions through your configured notification channels. Reply and the fix resumes. Configure timeout and best_effort_on_timeout in [ask]. Claudear remembers previous answers so the same question is not asked twice.
#Day-to-day workflows
Check what's happening
claudear status, claudear activity, or open the dashboard.
Trigger a manual fix
claudear trigger linear ABC-123 or claudear trigger sentry 12345
Retry a failed fix
claudear reset sentry 12345 or claudear retries process
Generate a report
claudear report preview daily or claudear report send weekly
#Advanced features
Regression monitoring
Watch for errors reappearing after a fix is merged.
→Cascading fixes
Propagate fixes across dependent repositories automatically.
→Learning from results
Extract knowledge from diffs, Q&A, and reviews to improve future fixes.
→Issue prioritisation
Rank issues by severity, frequency, blast radius, and more.
→Repository management
Discover, index, search, and manage repo dependencies.
→