Triage at the codebase, not just the ticket
Your agents listen where work happens—Jira, Telegram, Slack—and answer with grounded, repo-level insight, not generic filler. One core; plugins and config define the rest.
Pull image
docker pull ghcr.io/toniop99/agent-detective:latest
Press 1–5 to jump sections (desktop)
Container-ready (GHCR), JSON + env configuration, Zod-typed options. Configuration hub · Docker
Exhibit A — case visualization
One core. Many sources.
Adapters and plugins turn webhooks and APIs into a single task shape—so the agent always runs the same way, no matter which tool rang the bell.
Case notes
Built for real incidents, not slide decks
“One process from signal to story—tickets in, diffs and comments out.”
- 01
Source-agnostic events
Webhooks and adapters become one task model—Jira, chat, or your own plugin. The agent runner does not care who knocked.
- 02
Repo-grounded analysis
Local repositories and matching connect incidents to the right tree. Output stays honest to the code you run.
- 03
Operator-ready
Express, health, metrics, structured logs, JSON and env. Ship with Docker from GHCR when you are done iterating locally.
Docket
From webhook to well-grounded write-up
The same path every time: normalize, analyze, answer. You keep control of config, secrets, and where the model runs.
- 1 Event arrives: Jira, Slack, or your adapter—normalized into a single task model.
- 2 The core agent uses local repo context and your matching rules to analyze and reason.
- 3 Output where you need it: issue comments, optional PR flow, and full observability trail.
Ready to wire your first incident?
The docs walk through plugins, config/default.json, Docker, and production checks—no guesswork.