feat: manage multi-window codex injection - #12
Merged
Conversation
Document the multi-window injection design and execution plan so the branch carries the target identity and validation rationale.
Track injected Codex targets by CDP target id and attach caller identity to bridge requests so target-scoped Helper actions resolve against the originating Codex window instead of target discovery order.
Expose Codex launch and injection sync from the Helper tray menu so users can bring Codex under Helper control without restarting the helper.
Report runtime activity from each injected Codex window and limit automatic port ownership work to the focused window so multi-window sessions do not race over shared Helper state.
Avoid local port binding races between tests that intentionally exercise bound and unavailable port behavior.
Accept settings files that still contain keys removed from earlier Helper runtime surfaces. This keeps existing local configs readable without re-enabling the removed features.
Attach the active Helper caller identity to bridge requests so routes can target the originating Codex window. Use that identity for DevTools routing and runtime activity diagnostics.
Add browser-level target discovery helpers for Codex pages, including Target.getTargets support and injectable target filtering. This provides the CDP foundation needed for multi-window injection management.
Update the Bun launcher to mirror the managed multi-window injection model used by the Tauri shell. Inject all current Codex targets, keep watching target changes, clean up disconnected bindings, and keep target event logs behind an explicit debug flag.
Deduplicate routine activity reports, throttle remote port sync attempts, and suppress successful noisy bridge request logs while keeping failures visible.
Track managed Codex startup and shutdown more directly so Helper can recover from stale CDP state, avoid proxy environment leakage, and keep the dev launcher aligned with the packaged Tauri flow.
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
1 participant
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.
Summary
Test Plan
Note: bun test currently exits without details on main as well, so it was not used as a merge gate.