Bugmole documentation

Bugmole is a QA MCP framework and autonomous smoke-testing CLI for guiding an agent from repository exploration to executable, evidence-backed verification.

What Bugmole does

• Explores a repository before planning.
• Turns real user journeys into explicit plans.
• Runs browser and application checks with retries and safety gates.
• Stores manifests, reports, progress, and evidence using project-scoped keys.
• Exposes results through a read-only dashboard and the Bugmole MCP server.

Start here

1. Getting started — install Bugmole and run your first exploration.
2. CLI reference — learn the main commands.
3. Bugmole MCP — connect an agent to the framework.
   • Use Bugmole from ChatGPT or Claude — the hosted connector and the Bugmole skill.
4. Configuration — configure runtime, LLM, MCP, and browser execution.
5. Sample tests — see what a Bugmole flow looks like, and the same journey in Playwright, Cypress, and Selenium.
6. Discover and debug — explore an app from its URL, and find out why a run failed.
7. GitHub App integration — link QA findings to GitHub issues.

Bugmole is designed to keep the execution boundary explicit: local project workers run the app and tests, while the hosted dashboard and registry coordinate authorized project runs and display evidence.