Triage
Review AI-powered suggestions for improving your agents, with root-cause analysis and dispatch to code-fixing tools.
Triage is where you review and act on AI-powered suggestions for improving your agents. Suggestions are triggered automatically by anomaly detection, or manually through AI Search queries, comments, and detections. Each includes root-cause analysis, confidence scoring, and actionable fixes ready to dispatch to code-fixing tools.
Getting Started
The Triage workflow in 4 steps:
-
Your traces are getting logged — Make sure traces are flowing into Neatlogs from your agents. Each trace contains the full execution context (spans, errors, latency, tokens, cost).
-
Set up code-fixing integration — Connect your IDE under Settings → Integrations. Choose Claude Code, Cursor, or Codex so you can dispatch fixes directly from Triage.
-
Investigate with AI Search — Use AI Search to ask questions about your traces:
- "Why did my costs spike?"
- "Find traces where the model hallucinated"
- "Show me failed tool calls"
AI Search returns matching traces and automatically creates suggestions.
-
Review & act in Triage — Suggestions appear in your Kanban board (Draft → Open → In Progress → Resolved). Click a card to review the root cause, confidence score, and recommended fix. Dispatch to your IDE when ready.
How Suggestions are Created
| Source | Trigger | Result |
|---|---|---|
| Auto-Triggered | Neatlogs detects cost spikes, latency anomalies, prompt regressions, or retrieval failures | Draft suggestion appears in your board |
| AI Search | You ask a question about traces in AI Search | Open suggestion created from the analysis |
| @Neatlogs Comments | You tag @Neatlogs in a trace comment with an issue | Neatlogs analyzes context and creates a suggestion |
| Detections | A detection rule fires across multiple traces | Pattern is surfaced as a suggestion |
The Kanban Board
Suggestions flow through four columns:
| Column | Status | Next Step |
|---|---|---|
| Draft | Auto-generated, needs review | Review & edit, then move to Open |
| Open | Ready to action | Assign to teammate or move to In Progress |
| In Progress | Being worked on | Track dispatch & merge status |
| Resolved | Fix shipped | Archive for future reference |
What's on Each Card
- Title & Severity — What to fix and how critical
- Confidence — 0–100% likelihood the suggestion is correct
- Triage Label — Category (prompt regression, cost anomaly, etc.)
- Linked Traces — 1–3 traces that triggered it
- Root Cause — Why it happened
- Recommended Action — How to fix it
- Dispatch Status — Badge showing if sent to Claude Code/Cursor and current status
Suggestion Categories
Suggestions are labeled so you can filter by type:
- Regressions:
prompt_regression(quality drop),silent_degradation(gradual loss) - Anomalies:
cost_anomaly(spending spike),latency_anomaly(slowdown) - Functional:
hallucination(false content),tool_contract_misuse(bad args),retrieval_miss(RAG failure),orchestration_inefficiency(wasted steps),guardrail_bypass(safety fail)
Find & Filter Suggestions
Search — Find by title, trace ID, or keywords (e.g., "timeout")
Filters — Stack multiple:
- Status (draft, open, in_progress, resolved)
- Severity (critical, high, medium)
- Label (prompt_regression, cost_anomaly, etc.)
- Source (auto, AI Search, comment, detection)
Time range — Last 24h, 7d, 30d, or custom
Open a Suggestion
Click a card to view:
Root Cause & Evidence
- What happened (AI analysis)
- Why it happened (evidence reasoning)
- Linked traces (1–5 examples)
- Confidence breakdown (how sure Neatlogs is)
Recommended Action
- Title (what to fix)
- Steps (ordered fix plan)
- Risk assessment (what could break)
- Verification (how to test)
- Rollback plan (how to revert)
Dispatch to IDE
- Click "Send to [IDE]" (Claude Code, Cursor, Codex)
- Select branch and tool
- Neatlogs sends full context + traces + root cause
- Track PR status in the badge
Collaborate
- Comment to discuss with teammates
- Tag @Neatlogs for follow-up analysis
- Visible to everyone with project access
Workflow States
Draft → Open → In Progress → Resolved
- Draft: Auto-generated, edit & refine before sharing
- Open: Visible to team, ready to assign & dispatch
- In Progress: Being worked on, track dispatch + PR status
- Resolved: Fix shipped, add resolution note, archive when done
Feedback
Mark as Accepted (once fixed)
- Click Accept when the fix ships
- Add optional resolution note
- Helps Neatlogs learn what works
Provide Feedback (if incorrect)
- Click feedback icon → "incorrect" or "not actionable"
- Explain why (helps improve future suggestions)
Tips
Prioritize — Filter to critical + high severity, sort by confidence score (highest first)
Before Dispatching — Review root cause, check linked traces, verify the action makes sense for your code
Tool Choice
- Claude Code: Multi-file refactoring
- Cursor: Single-file quick fixes
- Codex: Infrastructure/config changes
Collaborate — Assign to teammates, discuss in comments, track PR status