feat(atb2): handle_issue: a design pass, then a fix pass in the sandbox; PR body; outcome; agents run on Fable - #4636
Draft
ATX24 wants to merge 1 commit into
Draft
Conversation
…box; PR body; outcome; agents run on Fable The stage itself. For an Easy/Medium issue: a read-only design pass investigates and writes the plan; a fix pass implements it, encodes the repros as tests (routed per TEST_INSTRUCTIONS.md from the repros' expectations) and runs targeted checks; the pipeline re-runs the gate, writes the PR body in the team's shape (Problem / After this PR / Behavioral boundaries / Tests / Validation) and, in Live mode, lifts the worktree's push guard for the one push and opens (or updates) a draft PR. DryRun stops before the push — what the evals run. For a Hard issue the design pass's output becomes `Issue.design_doc` for the shepherd; no code change. The Claude Code CLI is run directly (`claude -p ... --output-format stream-json`), writing its own transcript so the record survives a kill at the budget; implement_fix / write_design_doc are LLM functions only so their $render_prompt / $parse companions render and parse. Both passes run on claude-fable-5 (ATB2_MODEL overrides); time budgets were recalibrated from the first eval (Easy 3600s, Medium 7200s). Every run leaves ~/.atb2/runs/<branch>/outcome.json: kind (fixed / hard / gate_failed / agent_stopped), why the agent stopped, turns, seconds, the gate and the report.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
This was referenced Aug 31, 2026
ATX24
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The stage itself. For an Easy/Medium issue: a read-only design pass
investigates and writes the plan; a fix pass implements it, encodes the
repros as tests (routed per TEST_INSTRUCTIONS.md from the repros'
expectations) and runs targeted checks; the pipeline re-runs the gate,
writes the PR body in the team's shape (Problem / After this PR /
Behavioral boundaries / Tests / Validation) and, in Live mode, lifts the
worktree's push guard for the one push and opens (or updates) a draft
PR. DryRun stops before the push: what the evals run. For a Hard
issue the design pass's output becomes
Issue.design_docfor theshepherd; no code change.
The Claude Code CLI is run directly (
claude -p ... --output-format stream-json), writing its own transcript so the record survives a killat the budget; implement_fix / write_design_doc are LLM functions only so
their $render_prompt / $parse companions render and parse. Both passes
run on claude-fable-5 (ATB2_MODEL overrides); time budgets were
recalibrated from the first eval (Easy 3600s, Medium 7200s).
Every run leaves ~/.atb2/runs//outcome.json: kind (fixed / hard
/ gate_failed / agent_stopped), why the agent stopped, turns, seconds,
the gate and the report.
Stack (bottom to top)
//#headersEach PR passes
baml check/baml fmt/baml teston its own; the top of the stack reproduces the reviewedbaml/feedback-part-3tools/atb2exactly. Supersedesbaml/feedback-part-3.