attest Security and privacy
Understand the boundaries of a test run.
Attest processes untrusted pull request content and preview pages. Run it only with a deliberate security and network configuration.
Credentials and browser isolation
The browser runs in a separate constrained worker. GitHub credentials and the Anthropic API key stay in the backend rather than the browser worker. Preview destinations and redirects are checked, and private networks are blocked by default unless an administrator explicitly allows an eligible host.
Test-account passwords are injected through a trusted operation rather than given to the model. However, the application under test can read values entered into its own page. Use disposable, low-privilege credentials and synthetic data.
Data and evidence
Bounded PR context and browser observations can be sent to Anthropic for execution and independent review. Review your provider's terms and data controls before enabling a run. Treat screenshots and evidence as sensitive: access is protected, and current run evidence expires after 14 days. Operator-managed backups require their own retention controls.
Signed GitHub webhooks, exact-SHA checks, constrained tools and evidence validation reduce risk; they do not make arbitrary preview code trustworthy or guarantee semantic correctness. Consult limitations before enabling QA. A private vulnerability-reporting channel has not yet been established.