Skip to content

feat(cli): launch throwaway browsers from the one connected to the relay - #36

Merged
jack-arturo merged 2 commits into
mainfrom
feat/connected-browser-path
Nov 11, 2026
Merged

jack-arturo merged 2 commits into
mainfrom
feat/connected-browser-path

Conversation

@jack-arturo

Copy link
Copy Markdown
Member

Summary

Throwaway launches were still aimed at Chrome. browser-hand browser-path reads the relay and returns the macOS executable of the browser that actually has the extension connected. If nothing is connected, it fails. It does not fall back to Chrome or the OS default browser.

Search's extension user-agent still says Google Chrome. The debugger stub says the host is Search, and that name wins for browser-path and doctor.

Test plan

  • cd cli-js && node --test test/*.test.js — 224 pass, including the alias-ordering case
  • Live browser-hand browser-path against Search returned /Applications/Search.app/Contents/MacOS/Search
  • Upstream daemon/ and cli/ are untouched

Notes for reviewers

  • macOS only. Other platforms get a clear error.
  • Resolution looks in /Applications, then ~/Applications only when the first directory has no match. Several matches are an error, not a guess.
  • A symlink is ignored until its name matches, so an alias listed first cannot hide the real bundle.
  • The remote-debug recipe resolves the executable before quitting the connected browser. Quitting first drops the relay, and browser-path will not answer.
  • Size: 891 changed lines. Most of that is the new resolver and its tests.
  • Hosted CI covers the upstream daemon and Rust CLI, not cli-js.

Local review (Codex gpt-6.1-sol, medium) fixed the alias-ordering miss and the recipe order before this PR opened. A follow-up note about fixture tests calling plutil was not applied: the command is macOS-only, and CI does not run cli-js tests.

Implementation harness: Cursor (Grok 4.7). GitHub identity: the operator's gh login; this session has no GitHub App token.

Search reports itself as Chrome in the extension user-agent, so browser-path and doctor prefer the name in the debugger stub and resolve that macOS app.
browser-path now records a bundle only after its name matches, and the remote-debug recipe resolves the executable before the connected browser is quit.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-11T06:41:11.118797Z 7894c28 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@jack-arturo jack-arturo added babysit:active Babysit agent is actively working this PR babysit:waiting-codex 👀 Codex reviewing current head and removed babysit:active Babysit agent is actively working this PR labels Nov 11, 2026
@jack-arturo

Copy link
Copy Markdown
Member Author

Babysit ready. Verified green at 7894c2895ddc9a0aed625ca3cabe41073a239c13.

Codex signed off this head with 👍 (settled by reaction; review state completed with no findings). No review threads. CI is green on all six checks. The agent did not merge.

@jack-arturo jack-arturo added babysit:ready 👍 Codex all clear + gates pass; human may merge and removed babysit:waiting-codex 👀 Codex reviewing current head labels Nov 11, 2026
@jack-arturo
jack-arturo merged commit 598b8df into main Nov 11, 2026
6 checks passed
@jack-arturo
jack-arturo deleted the feat/connected-browser-path branch November 11, 2026 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

babysit:ready 👍 Codex all clear + gates pass; human may merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant