simplify: companion just opens your normal Chrome#47
Merged
Conversation
The profile-copy approach added complexity and didn't reliably surface the user's sessions. Drop it entirely along with the --fresh/--live/copy machinery: `zero browser connect` now just launches the user's installed Chrome against their real profile (persistent context), which is the only approach that uses their actual live logins. Also open the profile Chrome LAST USED (read from Local State's profile.last_used) instead of hardcoding "Default" — a likely reason the copy looked logged-out for anyone whose sessions live in "Profile 1". Keeps the macOS keychain fix and the clear "quit Chrome first" lock error. Remaining flags are advanced-only: --cdp, --chromium, --user-data-dir, --profile.
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.
Why
The profile-copy approach added a lot of machinery and still didn't reliably show the user's sessions. Per feedback: drop the cleverness and just use normal Chrome.
Change
--fresh,--live, and all the clone/skip-list code.zero browser connectnow just launches the installed Chrome against the user's real profile (persistent context) — the only approach that uses their actual live logins.Local State→profile.last_used) instead of hardcodingDefault. This is a likely reason the copy looked logged-out: if the user's logins live inProfile 1, aDefaultcopy is empty.--use-mock-keychain) and the clear "quit Chrome first" lock error.--cdp,--chromium,--user-data-dir,--profile.Trade-off
Using real live sessions means Chrome can only be driven by one program at a time, so the user must quit their normal Chrome first. That's inherent to Chrome;
--cdpis the escape hatch for keeping Chrome open.Testing
tsc+ build clean. Needs on-machine check: quit Chrome, runzero browser connect, confirm a logged-in site shows signed-in.Supersedes the copy default from #45.
🤖 Generated with Claude Code