Repository navigation
fix(preview): preserve unknown outcomes in browser guidance - #832
Merged
Merged
Conversation
Keep native Preview fallback paths while preventing blind replay of unresolved mutations. Explain the ordinary server browser, optional companion placement, and the retained recording-evidence read without promising current recorder state or recovery after restart.
This was referenced Nov 5, 2026
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
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.
Preview guidance could steer agents to another browser after failures without explaining how to preserve an already-issued action whose outcome is unknown. Keep the existing fallback routes and thresholds, explicitly preserve unresolved effects and host/profile identity, and describe the optional recording-operation read within its actual limits.
The browser-host guides now explain that ordinary Preview needs no companion, when independent remote rendering is useful, and how host selection differs from ChatGPT provider authentication and workspace/SDK workflows. Existing saved host selections, tab bindings and capabilities are unchanged.
Validation: 29 focused instruction/injection tests pass; provider-core typecheck, changed-file lint/formatting, and strict boundary checks pass. The actual combined browser/device context is 3,913 bytes against its 4,000-byte limit. Independent Sol Max review found no actionable issues. No installed runtime or authentication state was changed.
Implementation: GPT-6.1 Sol (high); review: GPT-6.1 Sol (max), Codex harness in Jones Code.
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.