Public-safety boundary
- Blocker-aware research on a public safety site.
- A hard privacy boundary: no real VINs or personal data.
- Human-review routing before customer-facing safety decisions.
Setup
Use the CLI with a configured model profile. The example uses a sample make/model query and stays on publicnhtsa.gov pages.
Run it from the CLI
Expected output
Build it into an app
Production notes
- Domain policy:
nhtsa.gov. - Do not use a real VIN in public examples.
- Include source URLs with any safety summary.
- Add human review before using results in customer-facing safety decisions.
Inspect
- Debug UI for form state and visible filters.
- Steps for detail-page URLs.
- Status for blockers or unavailable pages.
- Recording for review.
Cleanup
For CLI-created browsers, cleanup is automatic. Close any browser you created separately while debugging withweb browser close <browser-id>.
Common failures
- If a flow asks for a real VIN, stop and switch to public make/model recall pages.
- If recall data looks ambiguous, preserve the source URL and send the result to human review.