# Bugspray

> Connected QA for developers and AI agents.

- [QA that connects expectations to evidence](https://docs.bugspray.io/index.md): Define what should work. Investigate what breaks. Keep validation tied to the exact change.
- [Run Bugspray locally](https://docs.bugspray.io/quickstart.md): Start with an isolated data directory and submit a synthetic finding.
- [Organize your product catalog](https://docs.bugspray.io/concepts/catalog.md): Give people and agents a shared description of the product.
- [Write expectations that can be checked](https://docs.bugspray.io/concepts/workflows.md): Separate durable workflow identity from an exact saved definition.
- [Connect expectations to test suites](https://docs.bugspray.io/concepts/test-suites.md): Declare intended coverage without turning declarations into test results.
- [Report, reproduce and verify findings](https://docs.bugspray.io/guides/findings-and-replay.md): Keep observed failures, deterministic replay and advisory exploration distinct.
- [Illustrate workflows with reference videos](https://docs.bugspray.io/guides/reference-videos.md): Show an expected interaction while preserving its saved context.
- [Connect your AI agent](https://docs.bugspray.io/guides/ai-agents.md): Use live MCP discovery and evidence-first reporting.
- [Register your existing test suites](https://docs.bugspray.io/guides/register-suites.md): Commit a manifest and retain exact candidate inventory bindings.
- [Read PR validation with confidence](https://docs.bugspray.io/guides/pr-validation.md): Separate proposed coverage, deterministic replay and actual CI evidence.
- [Connect GitHub, Linear and Slack](https://docs.bugspray.io/guides/integrations.md): Add issue tracking and notifications when you need them.
- [Choose how to run Bugspray](https://docs.bugspray.io/self-hosting/overview.md): Start locally, then select an operator-owned deployment path.
- [Self-host the Node server](https://docs.bugspray.io/self-hosting/node.md): Configure HTTPS, access control and private persistent storage.
- [Operate a Cloudflare deployment](https://docs.bugspray.io/self-hosting/cloudflare.md): Use private manifests and reviewed release gates for hosted tenants.
- [Upgrade and recover without losing evidence](https://docs.bugspray.io/self-hosting/upgrades.md): Back up the whole deployment, then validate the candidate on isolated data.
- [Configuration reference](https://docs.bugspray.io/reference/configuration.md): Distinguish server runtime, client settings and private operator configuration.
- [HTTP API and submission reference](https://docs.bugspray.io/reference/http-api.md): Discover the running contract and use bounded source references for extended APIs.
- [MCP tools and resources](https://docs.bugspray.io/reference/mcp.md): Use the deployment’s discovered schemas as the contract.
- [Troubleshooting](https://docs.bugspray.io/reference/troubleshooting.md): Resolve common setup and evidence problems without resetting data.
- [Contribute to Bugspray](https://docs.bugspray.io/contributing.md): Work from current source, preserve user data and make changes reviewable.
- [Source and operational references](https://docs.bugspray.io/reference/source-map.md): Find the authoritative contract without duplicating it into the site.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.