Repository navigation
fix(runtime): Explain unavailable browsers - #29
Merged
Merged
Conversation
stickerdaniel
changed the title
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.
Problem
I reproduced successful tab navigation on ChatGPT.app 26.1103.60933 after an unavailable-browser error. That error alone does not establish a version incompatibility.
Solution
Verification
79 tests, typecheck, lint, formatting and package installation pass. Fault injection fails the affected test. Real MCP calls verify tab navigation and error annotation. Review found no defects.
Implemented with Claude Opus 5.5 (high) and reviewed with GPT-6.1 Sol (xhigh) in Claude Code/Codex via T3 Code.