Start where the work is
Read your code and, when connected, open issues and deployment events.
Read your code and, when connected, open issues and deployment events.
Reproduce the bug and isolate its cause on a separate branch. Unconfirmed bugs stay unconfirmed.
See the test fail before the fix and pass after. Keep review and merging with your team.
How it works
An illustrative engineering run: investigate a bug, reproduce it, write a fix, and return a draft pull request with before-and-after test results.
FactoriesEngineering run
IdleIllustrative runTypeError: Cannot read properties of undefined (reading 'currency')fix(checkout): price a cart that has no region yet
fix/checkout-missing-region into main
Guardrails
Every fix ends as a draft pull request for you to review, change, or close.
Every pull request opens as a draft against your default branch. It never merges, closes issues, or replies to customers.
Text from issues, deployment events, and fetched pages is read as data, never as instructions.
Comments on the matching issue when one exists. Otherwise files a new labeled issue that links the pull request.
Works with your engineering stack
Reads recent deployments and their events to collect errors and failures.
Reads the code behind each error, checks the repository out to write the fix, and opens draft pull requests.
Reads open issues so a known bug gets a comment, and files a labeled issue for a bug nobody reported.
Runs your tests in the checkout to show the result before and after the fix.
Hobby is free with monthly credits. Pro is for heavier use. Eligible accounts can start Pro with a 7-day free trial.
What's included:
$1 daily login bonus
Everything in Hobby, plus:
Pay as you go
Multi-member teams
Free viewers
Beta Feature Opt-in
What a run reads, what it changes, and what stays with your team.
Have a question about your engineering workflow? Talk to us
Connect a repository and describe the work. Run again for independent issues or configure a recurring maintenance schedule.