mirror of
https://github.com/garrytan/gstack.git
synced 2026-05-02 11:45:20 +02:00
Garry Tan
ddea3ad1b7
Multi-word, skill-specific trigger keywords for GBrain's RESOLVER.md router. Each skill gets 3-6 triggers derived from its "Use when asked to..." description text. Avoids single generic words that would collide across skills (e.g., "debug this" not "debug"). These are distinct from voice-triggers (speech-to-text aliases) and serve GBrain's checkResolvable() validation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
89 lines
2.7 KiB
Cheetah
89 lines
2.7 KiB
Cheetah
---
|
|
name: setup-browser-cookies
|
|
preamble-tier: 1
|
|
version: 1.0.0
|
|
description: |
|
|
Import cookies from your real Chromium browser into the headless browse session.
|
|
Opens an interactive picker UI where you select which cookie domains to import.
|
|
Use before QA testing authenticated pages. Use when asked to "import cookies",
|
|
"login to the site", or "authenticate the browser". (gstack)
|
|
triggers:
|
|
- import browser cookies
|
|
- login to test site
|
|
- setup authenticated session
|
|
allowed-tools:
|
|
- Bash
|
|
- Read
|
|
- AskUserQuestion
|
|
---
|
|
|
|
{{PREAMBLE}}
|
|
|
|
# Setup Browser Cookies
|
|
|
|
Import logged-in sessions from your real Chromium browser into the headless browse session.
|
|
|
|
## CDP mode check
|
|
|
|
First, check if browse is already connected to the user's real browser:
|
|
```bash
|
|
$B status 2>/dev/null | grep -q "Mode: cdp" && echo "CDP_MODE=true" || echo "CDP_MODE=false"
|
|
```
|
|
If `CDP_MODE=true`: tell the user "Not needed — you're connected to your real browser via CDP. Your cookies and sessions are already available." and stop. No cookie import needed.
|
|
|
|
## How it works
|
|
|
|
1. Find the browse binary
|
|
2. Run `cookie-import-browser` to detect installed browsers and open the picker UI
|
|
3. User selects which cookie domains to import in their browser
|
|
4. Cookies are decrypted and loaded into the Playwright session
|
|
|
|
## Steps
|
|
|
|
### 1. Find the browse binary
|
|
|
|
{{BROWSE_SETUP}}
|
|
|
|
### 2. Open the cookie picker
|
|
|
|
```bash
|
|
$B cookie-import-browser
|
|
```
|
|
|
|
This auto-detects installed Chromium browsers and opens
|
|
an interactive picker UI in your default browser where you can:
|
|
- Switch between installed browsers
|
|
- Search domains
|
|
- Click "+" to import a domain's cookies
|
|
- Click trash to remove imported cookies
|
|
|
|
Tell the user: **"Cookie picker opened — select the domains you want to import in your browser, then tell me when you're done."**
|
|
|
|
### 3. Direct import (alternative)
|
|
|
|
If the user specifies a domain directly (e.g., `/setup-browser-cookies github.com`), skip the UI:
|
|
|
|
```bash
|
|
$B cookie-import-browser comet --domain github.com
|
|
```
|
|
|
|
Replace `comet` with the appropriate browser if specified.
|
|
|
|
### 4. Verify
|
|
|
|
After the user confirms they're done:
|
|
|
|
```bash
|
|
$B cookies
|
|
```
|
|
|
|
Show the user a summary of imported cookies (domain counts).
|
|
|
|
## Notes
|
|
|
|
- On macOS, the first import per browser may trigger a Keychain dialog — click "Allow" / "Always Allow"
|
|
- On Linux, `v11` cookies may require `secret-tool`/libsecret access; `v10` cookies use Chromium's standard fallback key
|
|
- Cookie picker is served on the same port as the browse server (no extra process)
|
|
- Only domain names and cookie counts are shown in the UI — no cookie values are exposed
|
|
- The browse session persists cookies between commands, so imported cookies work immediately
|