dogfoodlisted

# Dogfood Systematically explore a web application, find issues, and produce a report with full reproduction evidence for every finding. ## Setup Only the **Target URL** is required. Everything else has sensible defaults -- use them unless the user explicitly provides an override. | Parameter | Default | Example override | |-----------|---------|-----------------| | **Target URL** | _(required)_ | `vercel.com`, `http://localhost:3000` | | **Session name** | Slugified domain (e.g., `vercel.com` -> `vercel-com`) | `--session my-session` | | **Output directory** | `./dogfood-output/` | `Output directory: /tmp/qa` | | **Scope** | Full app | `Focus on the billing page` | | **Authentication** | None | `Sign in to user@example.com` | If the user says something like "dogfood vercel.com", start immediately with defaults. Do not ask clarifying questions unless authentication is mentioned but credentials are missing. Always use `agent-browser` directly -- never `npx agent-browser`. The direct binary uses the fast Rust client. `npx` routes through Node.js and is significantly slower. ## Workflow ``` 1. Initialize Set up session, output dirs, report file 2. Authenticate Sign in if needed, save state 3. Orient Navigate to starting point, take initial snapshot 4. Explore Systematically visit pages and test features 5. Document Screenshot + record each issue as found 6. Wrap up Update summary counts, close session ``` ### 1. Initialize ```bash mkdir -p {