FE-1724: Remove the model-facing Brunch question marker - #9741
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
1da0764 to
8173c53
Compare
|
GitHub locks base changes for PRs in a native stack. Closing this copy so FE-1724 can be recreated directly against main without disturbing the queued Voice stack. |
|
Superseded by #9742, recreated directly against main. The original review fix is included in the rebased branch. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8173c53. Configure here.
| seed: experiment.seed, | ||
| // Nothing computes until a control moves or an optimizer navigates. | ||
| startComputing: false, | ||
| requireSuccessfulRuns: experiment.requestActive === true, |
There was a problem hiding this comment.
Sweep keeps host-only success requirement
Medium Severity
requireSuccessfulRuns is fixed to true for the whole sweep session when a host request creates the experiment. After the assistant captures its result, requestActive is cleared and users are allowed to explore, but any later batch with a failed run still errors the experiment. User-created sweeps do not behave this way, so inspecting an AI optimization after completion can lock the experiment in an error state.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 8173c53. Configure here.


🌟 What is the purpose of this PR?
Remove the model-facing question replay marker so direct questions no longer require a marker tool call and extra model completion.
🔗 Related links
🚫 Blocked by
🔍 What does this change?
Pre-Merge Checklist 🚀
🚢 Has this modified a publishable library?
This PR:
📜 Does this require a change to the docs?
The changes in this PR:
🕸️ Does this require a change to the Turbo Graph?
The changes in this PR:
New responses intentionally do not offer “Repeat question”; historical marked questions remain compatible.
🐾 Next steps
None.
🛡 What tests cover this?
❓ How to test this?
📹 Demo
Not applicable; this removes internal tool orchestration without changing the rendered response.
Made with Cursor