open gstack browser

Other Community v0.2.0

Skill notes

When to invoke this skill

Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

First-run guidance (one-time)

If ACTIVATED is no (first skill run on this machine) AND the preamble printed a non-empty FIRST_TASK: value that is NOT nongit: show ONE short, project-specific line mapped from the token, as a heads-up, then CONTINUE with whatever the user actually asked — do NOT halt their task.

Voice

Direct, concrete, builder-to-builder. Name the file, function, command, and user-visible impact. No filler. No em dashes. No AI vocabulary: delve, crucial, robust, comprehensive, nuanced, multifaceted. Never corporate or academic. Short paragraphs. End with what to do. The user has context you do not. Cross-model agreement is a recommendation, not a decision. The user decides.

Completion Status Protocol

When completing a skill workflow, report status using one of: DONE — completed with evidence. DONE_WITH_CONCERNS — completed, but list concerns. BLOCKED — cannot proceed; state blocker and what was tried. NEEDS_CONTEXT — missing info; state exactly what is needed.

Operational Self-Improvement

Before completing, review the session for durable learnings and log each one — this step ALWAYS runs, it is not conditional on something feeling noteworthy (#2402: 43 of 44 learnings came from explicit /learn because "if you discovered" read as optional). A durable learning is a project quirk, command fix, pitfall, or pattern that would save 5+ minutes in a future session. If

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v0.2.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Bun
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Pre-flight cleanup

Before connecting, kill any stale browse servers and clean up lock files that may have persisted from a crash. This prevents "already connected" false positives and Chromium profile lock conflicts.

02
Step 1: Connect

This launches GStack Browser (rebranded Chromium) in headed mode with: A visible window you can watch (not your regular Chrome — it stays untouched) The gstack sidebar extension auto-loaded via `launchPersistentContext` Anti-bot stealth patches (sites like Google and NYTimes work without captchas) Custom user agent and GStack Browser branding in Dock/menu bar

03
Step 2: Verify

Confirm the output shows `Mode: headed`. Read the port from the state file: The port should be 34567. If it's different, note it — the user may need it for the Side Panel. Also find the extension path so you can help the user if they need to load it manually:

04
Step 3: Guide the user to the Side Panel

Use AskUserQuestion: Chrome is launched with gstack control. You should see Playwright's Chromium (not your regular Chrome) with a golden shimmer line at the top of the page. The Side Panel extension should be auto-loaded. To open it: 1. Look for the puzzle piece icon (Extensions) in the toolbar — it may

05
Step 4: Demo

After the user confirms the Side Panel is working, run a quick demo: Wait 2 seconds, then: Tell the user: "Check the Side Panel — you should see the `goto` and `snapshot` commands appear in the activity feed. Every command Claude runs shows up here in real time."

06
Step 5: Sidebar chat

After the activity feed demo, tell the user about the sidebar chat: The Side Panel also has a chat tab. Try typing a message like "take a snapshot and describe this page." A sidebar agent (a child Claude instance) executes your request in the browser — you'll see the commands appear in the activity feed as they happen.

07
Step 6: What's next

Tell the user: You're all set! Here's what you can do with the connected Chrome: Watch Claude work in real time: - Run any gstack skill (`/qa`, `/design-review`, `/benchmark`) and watch every action happen in the visible Chrome window + Side Panel feed

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.