A bug report lands. Hedy searches the code, walks the commit window, matches known failure patterns and names likely owners — with an honest confidence level on every conclusion. Strictly read-only: no code changes, no auto-assign.
Hedy investigates bugs read-only: it searches the codebase, narrows the commit time window around when the regression appeared, matches against a pattern library of known failure shapes, and attributes likely owners from code history. Every finding carries a self-rated confidence (HIGH/MEDIUM/LOW) and, under the evidence gate, quotes the exact lines and commits it relied on. It never edits code — one Hedy runs a full triage lane, not a chat seat.
Last updated: 20 July 2026
Stack traces, error strings and identifiers are extracted and searched across your repositories.
"Started recently" checks 7 days of commits; "always been there" checks 30. Deploy times narrow it further.
Every closed investigation adds to a pattern library — the triage gets sharper with each incident.
HIGH, MEDIUM or LOW, stated plainly. A wrong certainty is worse than an honest maybe.
A bug report lands and Hedy runs the investigation a whole triage rotation would. It searches the repository for the failing symptom, correlates it against a commit time window — the range of changes between the last known-good state and the first failure — and matches the trace against a pattern library of recurring failure shapes (null deref, race, off-by-one in pagination, migration drift). It resolves likely owners from commit history and code ownership, so the report arrives pre-routed instead of pre-argued.
Every conclusion is graded. Hedy self-scores each finding HIGH / MEDIUM / LOW: HIGH when the suspect commit, the reproducing code path, and the pattern all line up; LOW when it only has a symptom and a guess. Under the evidence gate, a claim cannot ship without quoting its source verbatim — the exact commit SHA, file, and lines. A LOW-confidence hunch is labeled a hunch, not dressed up as a root cause, so engineers spend review time on the HIGH ones.
This lane is read-only by construction, not by promise. Hedy holds no write path to your source during investigation — the default-deny whitelist governs every action, so it cannot push, force-push, or open a non-Draft PR. Any suggested fix is a Draft a human opens and merges. That constraint lives in config and code, per Hedy's iron rule that a limit written only in a prompt does not exist.
Because Hedy is self-hosted — Docker or K8s on your infrastructure, air-gap supported — your code never leaves your network to be triaged. It uses your own model keys, including local vLLM or Ollama, so no third party sees the repository. Retrieval respects the requester's ACL, and the whole run lands in an append-only audit log: which files were searched, which commits inspected, what confidence was assigned, and every source the answer quoted.