Skip to content

feat(studio): Suggest fix button in the Results pane after a failed run - #468

Open
pbertsch wants to merge 2 commits into
mainfrom
feat/studio-selector-fix-ui
Open

pbertsch wants to merge 2 commits into
mainfrom
feat/studio-selector-fix-ui

Conversation

@pbertsch

Copy link
Copy Markdown
Member

Summary

  • After a run with a failed test or step, the Results pane shows Suggest fix. It asks the model for one replacement ProbeScript line for the failed step and shows it under the results, with its rationale and a Copy button.
  • Nothing is written into the file.
  • Uses the backend SuggestSelectorFix from feat(studio): AI chat context is opt-in (last run, widget tree), redacted; backend for a selector fix #467. It needs the run_results AI-context switch, which stays off by default; with it off, the reason shows in a toast.
  • Regenerates the Wails binding for SuggestSelectorFix and the SelectorFix model (hand-written to match the generator output).

Test plan

  • npm run build (tsc and vite) passes
  • npm run test:device-view: 116/116
  • Manual: run a failing test with run_results on, click Suggest fix, copy the line

🤖 Generated with Claude Code

After a run with a failed test or step, the Results pane offers Suggest fix. It asks SuggestSelectorFix for one replacement ProbeScript line and shows it under the results with its rationale and a Copy button. Nothing is written into the file. The backend still requires the run_results AI-context switch, and the error appears as a toast when it is off.

Also regenerates the Wails binding for SuggestSelectorFix and the SelectorFix model, and updates the CHANGELOG and the Studio docs.
@pbertsch
pbertsch requested a review from a team as a code owner October 15, 2026 17:35
The README listed the AI chat pane as deferred, and said it spawns probe-mcp. It calls the Anthropic API directly with the user's own key. The new section covers the chat, the AI chat context switches (off by default) and Suggest fix, and links to the Studio page.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant