Zero source retention

When an AI coding agent writes tests for your project, it reads your codebase on your machine or in your CI — inside Claude Code, Codex, Cursor, Copilot or Gemini, where your source already is. Only test cases, results and evidence travel to BugMojo, over MCP or our REST API.

There is no “connect your repository so we can index it” step, because there is no index. That is a deliberate architectural decision, not a setting: our plugins run where your code already lives precisely so that your code never has to move.

Cloud Run is our optional hosted execution: a throwaway Playwright container that runs a published test plan version against a URL you have deployed, so a team with no CI still gets a nightly run with evidence. A job that reaches that container carries exactly five things — the spec text, the deployed URL, an environment name, a time budget, and a write-only API key scoped to one project and revoked when the job ends.

It carries no repository, no clone URL, no branch, no commit to check out and no path into your source, so there is nothing for the container to read even if it tried. It also never executes your playwright.config.ts: the configuration is generated by BugMojo, which means no webServer, no globalSetup, and no arbitrary code from your repository running on our infrastructure.

Each container runs one job and is destroyed. The specs written into it live in a temporary directory that is removed when the job finishes, and the container’s filesystem does not survive it.

There are two sources, and you choose per project:

1. BugMojo’s stored copy. When your agent writes a spec, a copy is saved on the immutable test-case revision. That copy is what a plan version pins, and it is what makes “this is exactly what we tested, at this version” a claim we can stand behind.
2. A narrow read of your repository. If you would rather your repository stay the source of truth, a GitHub App reads your tests/ directory and nothing else. The token is scoped to that read; no other directory is fetched, and the contents are used for the run and then discarded.

A trust statement you cannot check is a marketing sentence. These claims are enforced in code, in places you can point a reviewer at:

• The container’s job parser refuses a job that carries a repository, clone URL, branch, source path or GitHub token — it does not ignore the field, it rejects the job.
• Spec paths are normalised and must resolve inside tests/; anything that climbs out is refused before a byte is written.
• The container is built on the official Playwright image and contains no git client.
• The child process runs with an allow-listed environment, so a spec cannot read BugMojo’s own credentials, and every log line, warning and error is redacted of API keys before it is written.

If you are running a security review and want to see the runner, ask us — we will walk you through the image and the job contract.

See our Security overview, the subprocessor list, the Data Processing Agreement and our Privacy Policy. Questions about this page? Email security@bugmojo.com.