Security

Autonomy handles test targets, evidence, messages, and integration credentials. Treat every setup as an organization-scoped workflow with explicit secrets and access boundaries.

Secrets

Never place API keys, preview bypass values, OAuth secrets, or static test account passwords in MDX, plans, or PR comments. Store them in environment variables or provider secret stores.

Evidence access

Run evidence belongs to the organization that created the run. Share evidence links only with people or systems that should be able to see screenshots, messages, network details, and logs from the target environment.

Execution boundaries

Hosted execution needs network access to the target surface. Private execution keeps the run inside your infrastructure while reporting evidence metadata and artifacts back to Autonomy according to organization settings.

MCP

Public MCP setup uses the server URL and browser authorization flow. Normal MCP clients should not require additional security configuration beyond the remote server connection and user authorization.