Skip to content

feat(autofix): Add retry buttons to Autofix v3 step cards#112290

Draft
isaacwang-sentry wants to merge 5 commits intoisaacwang-sentry/feat/autofix-retry-from-step-flagfrom
isaacwang-sentry/feat/autofix-retry-from-step-ui
Draft

feat(autofix): Add retry buttons to Autofix v3 step cards#112290
isaacwang-sentry wants to merge 5 commits intoisaacwang-sentry/feat/autofix-retry-from-step-flagfrom
isaacwang-sentry/feat/autofix-retry-from-step-ui

Conversation

@isaacwang-sentry
Copy link
Copy Markdown
Member

Add "Retry" icon buttons to completed step cards (Plan, Code Changes, Pull Requests) in
the Autofix v3 Explorer drawer. Clicking the button re-runs that step on the existing run
without requiring feedback text — useful for iterating on Seer changes locally.

Gated behind the autofix-retry-from-step feature flag registered in #112287.
RootCauseCard is excluded since the header "Start Over" button already covers that case.

Depends on #112287

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 6, 2026
@isaacwang-sentry isaacwang-sentry force-pushed the isaacwang-sentry/feat/autofix-retry-from-step-ui branch from cab7212 to e7f6ee2 Compare April 6, 2026 20:59
@isaacwang-sentry isaacwang-sentry force-pushed the isaacwang-sentry/feat/autofix-retry-from-step-ui branch from e7f6ee2 to 0eca46e Compare April 6, 2026 22:05
isaacwang-sentry and others added 3 commits April 6, 2026 15:22
Add a "Retry" icon button to completed step cards (Plan, Code Changes,
Pull Requests) in the v3 Explorer drawer. Clicking the button re-runs
that step on the existing run without requiring feedback text.

Gated behind the `autofix-retry-from-step` feature flag so it only
appears for local Seer testing. RootCauseCard is excluded since the
header's "Start Over" button already covers that case.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When retrying from a step, pass the section's block index as
insert_index so Seer truncates all blocks after that point. This
ensures downstream sections (e.g. Code Changes after retrying Plan)
are removed and the normal NextStep flow resumes after the retried
step completes.

Changes:
- Add blockIndex to AutofixSection, tracked in getOrderedAutofixSections
- Add insertIndex parameter to startStep
- Pass section.blockIndex in retry button handlers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Retry buttons are now always visible on all completed step cards
including Root Cause. The feature flag check has been removed since
this is intended as a standard feature, not gated functionality.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Only show the synthetic PR and coding-agent sections when a completed
code_changes section exists. After retrying an earlier step, blocks
are truncated but repo_pr_states persists on the run state, causing
the PR card to remain visible and preventing NextStep buttons from
appearing.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- NextStep now skips synthetic sections (pull_request, coding_agents)
  when finding the last section, so correct next-step buttons appear
  even when stale PR data persists
- CodeChangesNextStep shows "Yes, update the PR" when a PR already
  exists, "Yes, draft a PR" otherwise
- PullRequestsCard shows "Update" button when code has changed since
  the PR was last pushed, "View" link when in sync

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant