Skip to main content
Auto-fix is available on the Team plan and above.

​
How It Works

When an error group has a high-confidence AI triage result and your GitHub repository is connected, Squasher can attempt an automatic fix:
1

Secure sandbox created

Squasher creates a secure, ephemeral sandbox environment and clones your repository.
2

Patch generated

The AI analyzes the error, stack trace, and affected source files, then generates a unified diff patch.
3

Patch applied and tested

The patch is applied in the sandbox. If your repo has tests, they run inside the sandbox.
4

PR created

If the patch applies cleanly (and tests pass if present), Squasher creates a pull request on GitHub with a description linking back to the error group.
5

Sandbox destroyed

The sandbox is destroyed immediately after the PR is created. No persistent access to your code.

​
Security

  • Your code is cloned into an ephemeral sandbox that is destroyed after use
  • Squasher uses a GitHub App token scoped to your repository — it cannot access other repos
  • Patches are applied and tested in isolation — never on your production infrastructure
  • You review and merge the PR yourself — Squasher never pushes directly to your main branch

​
Triggering a Fix

Auto-fix can be triggered two ways:
  1. Manually — Click “Generate Fix” on any error group detail page
  2. Automatically — Enable auto-fix in project settings to run on new critical or high severity errors

​
Requirements

  • GitHub repository connected in project settings
  • Team plan or above
  • Repository must be accessible via the Squasher GitHub App