browse

When to invoke

Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this".

Preamble

eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
  fi
else
  echo "LEARNINGS: none yet"
fi

{{include lib/snippets/session-host.md}}

{{include lib/snippets/decision-brief.md}}

{{include lib/snippets/working-protocols.md}}

{{include lib/snippets/state-protocols.md}}

browse: QA Testing & Dogfooding

Persistent headless Chromium. First call auto-starts (~3s), then ~100ms per command. State persists between calls (cookies, tabs, login sessions).

SETUP (run this check BEFORE any browse command)

B="${CLAUDE_SKILL_DIR:-$HOME/.claude/skills/browse}/bin/vibe-browse"
[ -x "$B" ] || B="$(command -v vibe-browse || true)"
if [ -n "$B" ] && [ -x "$B" ] && [ "$("$B" status 2>/dev/null)" != "BROWSE_NOT_AVAILABLE" ]; then
  echo "READY: $B"
else
  echo "NEEDS_SETUP"
fi

vibe-browse is a launcher, not the browser itself. With the checkout's dependencies installed it runs the full daemon this file documents; without them it falls back to a stateless shim that covers navigation, capture and chain but answers NOT_SUPPORTED:<verb> to the interaction and inspection verbs. Read that answer as a missing capability rather than a transient failure: name the verb that was unavailable instead of retrying it or describing output you never got.

If NEEDS_SETUP — node is absent, or the first-run dependency install was declined — say which piece is missing, then fall back to text-only QA (curl plus structural HTTP checks) and report BROWSE_NOT_AVAILABLE. Do not trust a bare curl status code: dev servers happily serve error pages with HTTP 200, so grep the response body for the app's error markers before calling a page healthy, and tell the user screenshots were unavailable.