WORKFLOW · FIX THE BUG
From bug report
to PR.
Post the error message. Your agent clones the repo, reproduces the bug, finds the root cause in logs, writes a fix, runs the test suite, and opens a PR for your review.
Our widget service returns 500 on DELETE /widgets/:id when the widget has 3 or more linked components. Fix it.
- Pull request #487
- Failing test case (now passing)
- Code diff with comments
UseAgentExample workflowOur widget service returns 500 on DELETE /widgets/:id when the widget has 3 or more linked components. Fix it.
Clone and search
Cloned repo, found DELETE handler in handlers/widgets.ts. Searched error logs. Every 500 has 'permission check failed' after component count check.
Reproduce locally
Set up test DB with 3 linked components, sent DELETE request, confirmed 500. Traced the stack: permission middleware runs after cascade check, causing the 500.
Fix the order
Moved permission check before cascade. Added test case: DELETE with 3+ components now returns 204. Old test suite still green.
Open PR
Created PR #487: 'Fix widget delete with linked components'. Added test case to prevent regression.
TOOLS IT REACHES
THE RESULT
PR #487 opened. Tests pass. Ready for review.
Questions, answered.
What if the fix is complex and needs multiple commits?
Agent creates a single PR with multiple commits. You can review the full diff or commit-by-commit. Approve and merge when ready.
What if the agent can't reproduce the bug?
It'll tell you. The run will show what it tried, why reproduction failed, and what info is needed. You can reply with more context.
Can the agent create the PR automatically or does it wait for approval?
Agent creates the PR and waits. You review and merge. GitHub write operations require your approval (current state: read-only, write tools on the roadmap).
Start with one task.
See what you can hand off.
Explore a completed run, or join the early-access list to hear about getting your team started.