SOC 2 Type II audit in progress · EU, US and India data residency · a DPA you can sign
Trust Center →Repo Agent
Reads your codebase, not just the error.
When a ticket is code-adjacent, the Repo Agent searches the linked repository for the likely cause and attaches the probable files — the step most helpdesks skip entirely.
- Read-only by default
- GitHub & GitLab
- Files attached to the ticket
reading linked repogithub.com/acme/api
SENTRY · TypeError: cannot read property 'id' of undefined
searching repository
- src/checkout/cart.tsqueued
- src/checkout/payment.tsqueued
- src/lib/session.tsqueued
- src/api/routes.tsqueued
- src/lib/logger.tsqueued
✓ attached 0 files to the ticket · likely cause: cart.ts:142 — null guard missing after deploy a1f2c
Where it sits in the run
The Repo Agent goes first, so no one starts blind.
Every ticket runs the same path. The Repo Agent’s reading is what lets the rest of the run — and any human who does get involved — begin from a real diagnosis.
- 01 · you are hereRepo AgentReads the repo, attaches the likely files.reads github · gitlab
- 02Triage AgentPriority and owner from real impact./agents/triage →
- 03Resolution AgentRuns the allow-listed fix, verifies, closes./agents/resolution →
- Reads GitHub
- GitLab
- Triggered by Sentry
- Datadog
- Slack
1st
It is the step most helpdesks skip. They route the words; the Repo Agent routes the cause. By the time a ticket reaches a queue, the probable files are already attached — which is most of why so many never need a person.50% is the mean across our published customers — how we count an auto-resolution.
Point it at your repo. Watch the next ticket arrive diagnosed.
Read-only to start. Connect a repository and the very next code-adjacent ticket shows up with the likely files attached.