Add macOS and Windows cross-platform session bridge - #1
Draft
streetlightstartupnotes wants to merge 2 commits into
Draft
Add macOS and Windows cross-platform session bridge#1streetlightstartupnotes wants to merge 2 commits into
streetlightstartupnotes wants to merge 2 commits into
Conversation
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.
What changed
Why
The browser grid must control the same Codex Session on macOS and Windows while submitting each user message exactly once. The Windows implementation mirrors the macOS contract: open the target task, fill the native composer, submit once, then let the grid poll the same Session.
Validation
Manual test still required
A real interactive Windows 11 desktop is still required to confirm the current Codex/ChatGPT App UI Automation element names and the
codex://task deep link. Followdocs/WINDOWS_TESTING.mdand confirm that one web send produces exactly one App message and one Session response.