Feature request: CLI command to capture & summarize API flows

Summary

Add a CLI command to analyze live API traffic while browsing a page.

Current State

• agent-browser network requests lists request metadata only
• responsebody action exists in src/actions.ts but is not exposed via CLI

Proposed CLI Commands

# View all captured traffic from the live session
agent-browser network dump --out flow.json

# View response body for a specific request
agent-browser network response <request-id>

Core Output

• Method, URL, status code
• Request/response headers (with redaction for auth/cookies/PII)
• Response body (truncated by default)
• Timing data

Signal vs Noise Filtering

Priority filters:

1. Host/path allowlist — isolate real APIs from CDN/ads/analytics
2. Resource type filters — keep xhr/fetch, drop image/font/stylesheet/script
3. Path templating — collapse IDs/UUIDs to {id} for stable endpoint grouping
4. Auth/CSRF detection — flag headers/cookies indicating login/session flows
5. Query-key heuristics — identify search/catalog flows (q, query, search)

Nice-to-Have Features

• Diff support — compare against baseline (new/removed/changed endpoints)
• GraphQL awareness — detect /graphql, infer operation names
• WebSocket signals — handshake info and frame summaries
• Warnings — flag missing/blocked responses or truncated payloads
• Config file — persistent include/exclude rules for hosts/paths/mimes
• Exports — OpenAPI, Postman, curl, replay-json

MVP

If only one capability is added: response status + response body (with redaction + truncation). This enables accurate classification, exports, and diffs.

Start by reviewing the existing agent-browser network requests command and the responsebody action in src/actions.ts to understand the current capture and response-body paths. Define the MVP around response status and a truncated, redacted response body for a selected request; done should include the proposed CLI entry point and coverage for the stated output behavior.