ghostonbutterbread/chromium-test

Chromium Test

Use when a task needs a fresh Chromium/Chrome instance with remote debugging enabled, an isolated profile, and MITM proxy observation.

Use this for live browser exploration, not as the default replay transport. When Ryushe says to look at a URL, application, or flow, launch Chromium/Playwright with the agent's local browser proxy attached so requests generated by the browser can be observed in the agent lane.

Also use this when a deep-map, URL-list, or raw replay run hits Cloudflare/managed challenge pages, browser-only tokens, TLS/header fingerprint issues, or other bot-defense behavior before app content is visible. A plain 403/401 is not enough by itself; classify normal app/server forbidden responses with /403, /error-triage, auth, access-control, or header reasoning first. For real challenge/fingerprint/browser-only cases, escalate into a proxied browser context instead of treating raw HTTP as app-layer coverage.

The launcher prefers Playwright's bundled Chromium when Playwright is installed, then falls back to system Chromium/Chrome.

Invocation

/chromium-test <program> <task> [--url <url>] [--port <port>] [--remote-allow-origins <value>]
/chromium-test superdrug pfp
/chromium-test canva upload-flow --account-label qa-primary --url https://www.canva.com/

MITM Proxy Certificate Handling

The launcher should trust the proxy CA inside each isolated Chromium profile. Do not use blanket certificate-ignore mode as the normal path.

Default behavior:

• --proxy-cert-mode auto: import the mitmproxy CA into the profile when possible; fall back to --ignore-certificate-errors only when certutil or the CA file is missing.
• --proxy-cert-mode import: require CA import and fail if it cannot be prepared.
• --proxy-cert-mode ignore: explicit disposable debugging mode.
• --proxy-cert-mode none: attach the proxy without CA setup or ignore flags.

Standalone profile preparation:

bash "$HARNESS_ROOT/skills/chromium-test/scripts/install.sh"
python3 "$HARNESS_ROOT/skills/chromium-test/scripts/mitm_chromium_profile.py" \
  --profile-dir "$HARNESS_SHARED_BASE/<program>/ghost/chromium-test/profiles/<account>" \
  --home-dir "$HARNESS_SHARED_BASE/<program>/ghost/chromium-test/profiles/<account>/home" \
  --ca-cert ~/.mitmproxy/mitmproxy-ca-cert.pem

Hoster/default proxy model:

• http://hoster:8080 is the default always-on capture proxy for generic curl, httpx, and script traffic when no task-specific browser lane is needed. Ensure it is running with:

  python3 "$HARNESS_ROOT/skills/chromium-test/scripts/hoster_mitm_lane.py" --json ensure-default
  

• http://hoster:8081 through http://hoster:8090 are leased per-agent MITM lanes. Acquire a lease before starting a task-specific proxy and release it after indexing the lane into the central proxy store.
• On Ryushe's PC (abommie/ryushespc), prefer the local MITM proxy lane unless the task explicitly asks for Hoster routing.

Lease-backed mitmproxy lane smoke:

python3 "$HARNESS_ROOT/skills/chromium-test/scripts/hoster_mitm_lane.py" --json acquire-start \
  --agent-id <agent-id> \
  --run-id <run-id> \
  --program <program> \
  --task "<task>" \
  --account-label <account-label>
python3 "$HARNESS_ROOT/skills/chromium-test/scripts/chromium_test.py" <program> "<task>" \
  --proxy-server http://hoster:<leased-port> \
  --ephemeral-profile \
  --run-id <run-id> \
  --agent-id <agent-id> \
  --account-label <account-label> \
  --proxy-cert-mode import \
  --mitm-ca-cert ~/.local/state/ghost/mitm-lanes/<lane>/mitmproxy/mitmproxy-ca-cert.pem
python3 "$HARNESS_ROOT/skills/chromium-test/scripts/hoster_mitm_lane.py" --json index-stop-release \
  --lane <lane> \
  --agent-id <agent-id> \
  --run-id <run-id> \
  --account-label <account-label> \
  --proxy-port <leased-port> \
  --transport browser
ssh -i /home/ryushe/.ssh/hoster -o BatchMode=yes -o ConnectTimeout=10 -o ControlMaster=no -T \
  ryushe@hoster 'cd /home/ryushe/projects/bug_bounty_harness && python3 skills/chromium-test/scripts/proxy_store.py query --program <program> --method POST'
python3 "$HARNESS_ROOT/skills/chromium-test/scripts/proxy_store.py" export-request --id <request_id> --output /tmp/request-packet.json
python3 "$HARNESS_ROOT/skills/chromium-test/scripts/chromium_test.py" cleanup-profile --profile-dir <profile-dir> --json

Required Preflight

1. Read program scope/rules and the interpreted rate limit before live interaction.
2. Read $HARNESS_ROOT/prompts/chromium-test-playbook.md.
3. Check existing program context under $HARNESS_SHARED_BASE/{program}/.
4. Resolve browser/account state from explicit task context or a locked-down auth seed file. Do not query external profile services during browser launch.
   • If --auth-seed-file is not provided, --account <alias-or-color> or --account-label <alias-or-color> may resolve $HARNESS_SHARED_BASE/{program}/credentials/account_inventory.json.
   • Account inventory entries are non-secret pointers only. They may include credential_ref or auth_seed_ref values such as auth-seed:/absolute/path/to/seed.json, but never cookie/token/header values.
   • If Ryushe explicitly requested that account/color and the auth seed is missing, stale, or fails, follow the account record's auth_refresh_source and auth_refresh_hint. For auth_refresh_source=ryushe-proxy, load /ryushe-proxy, refresh only that selected account's seed, and never print or persist the raw values anywhere except the locked-down seed file.
5. If Ryushe names an account/profile, for example "use blue to go look at X", use that scoped account context. If the needed account/profile is unclear, ask before borrowing or creating auth state.
6. If the task needs live intercept/modify/forward behavior, read intercepted-proxy before launching the browser.
7. Confirm the MITM proxy setup:
   • Browser proxy defaults to the runtime route table and may be overridden by --proxy-server or $CHROMIUM_TEST_PROXY_SERVER.
   • Every normal launch must include a browser proxy and a trusted proxy CA in the isolated profile. Explicit certificate-ignore mode is fallback/debug only.
   • On OpenClaw/Ghost/ghostonbread, the default agent-lane browser proxy is http://hoster:8080; on hoster or ryushespc/Abommie, use http://localhost:8080.
8. For curl-failure escalation, inject only approved agent-owned or auth-seed auth/session material into the browser context. Use it in memory only; never print, store, or summarize raw cookies, bearer tokens, CSRF tokens, or private headers.

Canonical Files

• Playbook: $HARNESS_ROOT/prompts/chromium-test-playbook.md
• Launcher: $HARNESS_ROOT/skills/chromium-test/scripts/chromium_test.py
• Profiles: $HARNESS_SHARED_BASE/{program}/ghost/chromium-test/profiles/
• MITM profile helper: $HARNESS_ROOT/skills/chromium-test/scripts/mitm_chromium_profile.py
• MITM lane helper: $HARNESS_ROOT/skills/chromium-test/scripts/mitm_lane.py
• Hoster lane helper: $HARNESS_ROOT/skills/chromium-test/scripts/hoster_mitm_lane.py
• Sanitized proxy store: $HARNESS_ROOT/skills/chromium-test/scripts/proxy_store.py
• Dependency installer: $HARNESS_ROOT/skills/chromium-test/scripts/install.sh
• Notes/evidence: $HARNESS_SHARED_BASE/{program}/ghost/chromium-test/

Workflow

1. Start an isolated browser with the launcher:

   python3 "$HARNESS_ROOT/skills/chromium-test/scripts/chromium_test.py" <program> "<task>"
   

   The launcher resolves the runtime route and adds --proxy-server=<mitm-proxy> by default.
2. Use the returned CDP URL to connect browser automation or manual debugging.
3. For challenge/fingerprint/browser-only escalation, revisit the blocked URL in this browser profile before running more probes. Confirm whether the app layer, JS, route params, and proxy-observed requests are now visible.
4. Perform only the requested scoped action in that browser profile.
5. Observe traffic through the approved MITM proxy workflow when configured. Index finished mitmproxy lanes into the proxy store with sanitized default query output and full local request-packet export for replay:

   python3 "$HARNESS_ROOT/skills/chromium-test/scripts/mitm_lane.py" --lane <lane> index-store
   python3 "$HARNESS_ROOT/skills/chromium-test/scripts/proxy_store.py" query --program <program> --method POST
   python3 "$HARNESS_ROOT/skills/chromium-test/scripts/proxy_store.py" export-request --id <request_id> --output /tmp/request-packet.json
   

6. If a replay is needed after capture, hand the sanitized request shape to direct HTTP replay through MITM first.
7. Close and delete disposable browser profiles after the lane has been indexed unless Ryushe explicitly asks to preserve the profile for manual debugging.
8. Stop the proxy lane and release its lease so another agent can use the port.
9. Save screenshots, request notes, and reproduction details under the program evidence directory.

Guardrails

• Core posture: scoped testing is allowed; damaging behavior is explicit.
• Never reuse Ryushe's normal browser profile.
• Never print secrets, cookies, or credentials in chat.
• Never paste exported full proxy request packets into prompts or chat; they may contain cookies, bearer tokens, CSRF values, API keys, or request body secrets. Use sanitized query output for agent context.
• Auth seed files must be local JSON files with owner-only permissions such as 0600. The launcher may report safe metadata and which secret field names exist, but must never print cookie, bearer, CSRF, or token values.
• Verify the launch command includes --proxy-server=<browser-proxy> and that proxy_cert_status is trusted when proxy TLS interception is expected. If the launcher falls back to --ignore-certificate-errors, record that as debug/fallback behavior.
• Live browser traffic should be observed from this browser's MITM proxy lane. Do not pull live browser requests from Ryushe's proxy unless Ryushe specifically asks for Ryushe-lane comparison or request lookup.
• Named-account auth fallback is allowed when Ryushe asked for that account, for example "blue credentials", and the account inventory explicitly permits auth_refresh_source=ryushe-proxy. Use Ryushe's proxy only to refresh the seed for that account, then test through the agent MITM lane.
• Direct HTTP replay is preferred after a live request is captured and should use curl -x <mitm-proxy> when request logging is desired.
• For intercepted proxy testing, do not launch the browser until the resolved --proxy-server=<browser-proxy> value is known. Route to intercepted-proxy for the intercept on/off and temporary Tamper rule lifecycle.
• Stay inside the program scope, account authorization, and rate limits.
• For state-changing tasks, confirm the action is allowed and non-destructive before proceeding.