Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From helium-browser
Start the persistent Helium MCP gateway (one browser connection, no repeated approval prompts)
How this command is triggered — by the user, by Claude, or both
Slash command
/helium-browser:helium-startThe summary Claude sees in its command listing — used to decide when to auto-load this command
Start the persistent Helium browser MCP gateway. ## Steps 1. Run: 2. If Helium shows a remote debugging approval dialog, click **Allow once**. The gateway keeps that session alive — later agent turns will not re-prompt. 3. Verify with: 4. To stop the gateway: For zero approval prompts across restarts, close Helium and launch with `scripts/launch-helium-with-debug.sh` instead of the normal app shortcut.
Start the persistent Helium browser MCP gateway.
Run:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/start-persistent-server.sh
If Helium shows a remote debugging approval dialog, click Allow once. The gateway keeps that session alive — later agent turns will not re-prompt.
Verify with:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/status.sh
To stop the gateway:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/stop-persistent-server.sh
For zero approval prompts across restarts, close Helium and launch with scripts/launch-helium-with-debug.sh instead of the normal app shortcut.
npx claudepluginhub awfixers-stuff/plugins --plugin helium-browser