Issues and alerts
AI fix
The AI fix panel on an issue page sends the latest event's stack trace, breadcrumbs and request (query string removed) to Claude and returns a summary, the likely cause, a fix and a confidence level, plus a copy-ready prompt for Claude Code or Cursor. Connect a GitHub repository and it also reads the files in the stack trace at the commit of the release that crashed, can open a pull request with the fix and a test, and learns from similar issues you fixed before. Everything it reads is framed as untrusted data, so text in an error or in your code cannot steer the model.
1Buy credit
On Usage, buy an AI credit pack of $5, $20 or $50 through a one-time Stripe Checkout. The balance is shared by the workspace and never expires.
2Connect GitHub (optional)
Project, GitHub, Connect GitHub installs the Blipit.io GitHub App on your account or organisation, and you choose which repositories it can see. Then pick the repository, the default branch, the root path for a monorepo, and how releases map to commits: the release is a git commit (3f2a9c1 or web@3f2a9c1), the release matches a tag pattern such as v{release}, or always the default branch. A release registered through the CLI or API with a commit always uses that commit. Only owners and admins can change this; members can see it.
3Run a fix
Owners and admins pick a model and press run; results appear for everyone on the issue. Claude Haiku 5.5 is fastest and cheapest, Sonnet 5.5 balanced, Opus 5.5 most thorough. It usually takes 10 to 90 seconds. One fix runs per issue at a time and three per workspace. Code the AI read lists each file with the lines sent, the commit and why it was read; when the release could not be matched to a commit, it says the default branch was read instead.
4Open a pull request
After an analysis, Open pull request asks Claude for the smallest change plus a test. Blipit checks that every edit applies cleanly to the current default branch and refuses edits to CI files, secrets, dependency manifests and lockfiles, then pushes a new branch blipit/fix-<issue> and opens a pull request with the explanation, a link back to the issue and the labels blipit and ai-fix. Nothing is ever pushed to your default branch, and your branch protection and checks apply as usual. The issue shows the pull request and whether it was merged.
5How you are charged
Each model shows its typical price next to its name before you run it, and Open pull request shows its price on the button. Before the call, the worst-case price is held from your balance; afterwards the real price is charged and the rest returned at once. A refusal, a cut-off answer, an API error or a pull request that could not be opened releases the whole hold, and any hold older than 15 minutes is released on the next visit. Every purchase and charge is in the ledger on Usage.
6Live data on pull requests
On Scale, when a GitHub pull request changes lines of code behind open errors or slow Odoo queries, Blipit posts one comment on the pull request and updates it on every new commit. Errors from every stack are matched through their stack traces. It is exact matching, not AI, so it uses no AI credit. Turn it on or off per project on the project's GitHub page.
- Open errors on the changed lines, each with its event count, when it was last seen and a link to the issue.
- In Odoo: slow actions that run queries from the changed lines, with the repeated queries, the slowest run and a link to Pulse.
- Errors and slow queries elsewhere in the changed files, in a collapsed section.
- Blipit reads only the list of changed files, their changed line numbers and the file tree. No code is sent to AI, and query text never leaves Blipit.
Good to know
- Typical prices for a 6,000-token report: under $0.01 with Haiku 5.5, about $0.11 with Sonnet 5.5 and $0.22 with Opus 5.5. With a connected repository a run reads more, typically $0.02, $0.34 and $0.68, and a pull request is typically $0.03, $0.68 and $1.36. Long stack traces and large files cost more; the report is capped at 40,000 characters and the code at 12 files and 120,000 characters.
- What is sent where: the error report goes to Anthropic's API when someone runs a fix. With GitHub connected, Blipit fetches the files in the stack trace and the files they import from GitHub at that moment and sends them to Anthropic with the report. Files that look like secrets (.env, keys, certificates, credentials, service-account files) are never read, secret-looking values such as API keys and private keys are replaced before sending, and vendored, built and binary files are skipped. Blipit keeps only the file paths and the commit with the analysis, not the code.
- The GitHub App asks for Contents read and write (read files; write only to push the blipit/fix- branch), Pull requests write (open the pull request and see when it is merged) and Metadata read. Access tokens are created per run, limited to the one repository and expire within an hour; the app's private key is an encrypted server secret and never leaves the server.
- Similar issues: AI fix looks up resolved issues in the same project with a similar title or the same exception type and tells Claude which fix was accepted, either a Blipit pull request that was merged or an earlier analysis after which the issue was resolved. It never looks outside your workspace.
- Odoo: for issues from the Odoo module, Claude also gets the Odoo version and edition, the installed modules and their versions (custom ones by name), the model, method, workflow step and record state, the names of the fields being written, and links to the exact lines of Odoo's own code on github.com/odoo/odoo for that version. Record ids, field values and people's names are never sent.
- To disconnect, open Project, GitHub and press Disconnect; AI fix stops reading the code at once. To remove Blipit's access completely, uninstall the Blipit.io app in your GitHub settings; Blipit then forgets the installation. Connecting, disconnecting and every pull request are in the audit log.
- Nothing is sent to Anthropic unless someone runs a fix or opens a pull request. The privacy policy names Anthropic as a processor for this.
- Your coding agent can fetch the latest finished analysis, the files it read and its pull request through the MCP tool get_ai_fix.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.