Skip to content

feat(seer): Add browser-fetching autofixRef embed - #122099

Draft
ryan953 wants to merge 1 commit into
masterfrom
worktree-autofix-ref-embed
Draft

feat(seer): Add browser-fetching autofixRef embed#122099
ryan953 wants to merge 1 commit into
masterfrom
worktree-autofix-ref-embed

Conversation

@ryan953

@ryan953 ryan953 commented Aug 14, 2026

Copy link
Copy Markdown
Member

Adds autofixRef, a sibling to the autofix Seer markdown embed. Where autofix takes the full markdown write-up for a step as a prop ({step, result, id, shortId}) and has to be filled in by Seer once a run finishes, autofixRef takes just {step, id, shortId, runId} and fetches/polls the run itself in the browser via useExplorerAutofix — showing progress while the step runs, the result once it completes, and buttons to continue to the next step or retry on error.

This lets a caller (Seer's Code Mode, in a companion getsentry/seer change) emit the tag right after triggering a step instead of polling to completion and writing up the result first.

useExplorerAutofix's group parameter is narrowed from Group to Pick<Group, 'id' | 'shortId'> — it only ever read those two fields, and the embed only has an issue id/shortId, not a full Group. Existing callers are unaffected since Group satisfies the narrower type.

Includes an autofixRef.stories.tsx page with a live issue picker and root-cause/plan/code-changes trigger buttons for manual testing, and the regenerated embed_widgets.generated.json.

Not yet manually verified in a running browser — typecheck and lint pass, but the stories page itself hasn't been visually checked.

The existing autofix embed takes the step's full markdown write-up as a prop, which requires Seer to poll the run to completion and format the result before emitting the tag. Add a sibling autofixRef embed that instead takes only the issue id/shortId, run id, and step, and fetches/polls the run state itself in the browser via useExplorerAutofix — narrowed to accept Pick<Group, 'id' | 'shortId'> so it doesn't need a full Group. Once a step completes it shows continue/retry actions; this lets callers emit the tag immediately after triggering a step instead of waiting on it.

Includes a live-data stories page with an issue picker and step-trigger buttons for manual testing.
@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components 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