Make Helium the browser these configs drive - #68
Merged
Conversation
The day-to-day browser with the live SSO logins is Helium, a Chromium fork, not Google Chrome. Chrome's DevToolsActivePort is stale, so the default attach path fails and launching Chrome opens an empty profile. - claude/CLAUDE.md: Helium-first browser section — the helium://inspect/#remote-debugging toggle, the DevToolsActivePort -> ws:// endpoint recipe, and daemon start --endpoint for one consent prompt per session. - login-microsoft-sso: attach through Helium's endpoint before doctor. - Workday/Engage/Outlook skills: "real Chrome" -> "real browser" so the prose no longer names the wrong application.
The shared CLAUDE.md loads into every session, so it states policy, not mechanics. The endpoint recipe becomes a script both the rules and the skills call by path. - claude/scripts/browser-endpoint.sh: prints the CDP endpoint, exits 1 with an instruction when the port file is absent. - claude/CLAUDE.md: browser section cut from 25 lines to 10 — which browser, attach do not launch, which tool, one consent prompt, no credentials. - login-microsoft-sso: calls the script instead of repeating the recipe.
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.
The day-to-day browser with the live SSO logins is Helium (a Chromium fork), not Google Chrome.
chrome-cdp doctorandagent-browser --cdp 9222default to Chrome'sDevToolsActivePort,which is stale or absent, so the attach fails with
connection_failed;launching Chrome instead opens an empty profile with none of the logins.
Changes
claude/CLAUDE.md— the "Interacting with browser" section is Helium-first:the
helium://inspect/#remote-debuggingtoggle (no restart, tabs and logins survive),the
DevToolsActivePort→ws://endpoint recipe,and
chrome-cdp daemon start --endpointso the consent prompt is answered once per session.login-microsoft-sso— attach through Helium's endpoint beforedoctor,because
doctorreads Chrome's port file by default.so the prose no longer names the wrong application.
The
chrome-cdptool name is unchanged.Verification
make preflightandmake testpass.