Skip to content

docs: rewrite README hero with pain-first voice #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
oren153 merged 1 commit into from
Mar 10, 2026
Merged

docs: rewrite README hero with pain-first voice #38

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,13 @@

# agent-triage

**Debug the production flow of your AI agent system — find the exact step where it started failing, and how to fix it.**
**Stop staring at logs trying to figure out why your agent keeps failing.**

Point agent-triage at your production traces and system prompt. It reconstructs the conversation flow across agents, routers, handoffs, and retrieval steps — identifies the root cause moment, attributes the failure to the responsible agent or subsystem, aggregates recurring issues across conversations, and generates copy-paste fixes.
Point agent-triage at your production traces. It extracts behavioral rules directly from system prompts, replays each conversation step-by-step using an LLM-as-judge, and flags exactly which turn broke things, which agent caused it, and how failures cascade across routing, handoffs, and retrieval.

**Works for both single-agent and multi-agent systems.**
Then it aggregates root causes across all conversations — "24 out of 51 failures are missing escalations" — so you know exactly what to fix first.

**Works for both single-agent and multi-agent systems.** Runs locally. Only LLM API calls leave your machine.

- **Pinpoint the break** — See the exact step, turn, and agent where the conversation first went off track
- **See patterns across production** — Aggregate recurring failures across conversations by prompt, routing, handoff, or retrieval issue
Expand Down Expand Up @@ -125,7 +127,7 @@ npx agent-triage analyze --traces conversations.json --prompt system-prompt.txt
| `gpt-4o` | OpenAI | ~$0.65 | `--provider openai` |
| `claude-sonnet-4-6` | Anthropic | ~$0.90 | default |

**Privacy:** Traces stay on your machine. Only LLM API calls leave — no telemetry, nothing sent to us.
**Privacy:** No telemetry, nothing sent to us — only LLM API calls leave your machine.

## How it works

Expand Down