Issues
An Issue is not a single bad trace. It’s a recurring failure pattern across multiple sessions, with a root cause explanation and a proposed fix.
In the console, the Issues page shows a flat list. Filter by agent using the chips at the top; sort by Impact, Recent, or Created.
What an Issue contains
Section titled “What an Issue contains”| Field | Description |
|---|---|
| Title | Short name for the failure pattern, e.g., “Temporal / chronology confusion” |
| Description | One-sentence root cause, e.g., “Model focuses on incident type rather than liability context” |
| Tags | Failure category labels: missing_edge_cases, missing_context, vague_instructions, OPAQUE_TASK |
| Session count | How many sessions show this pattern. Higher = more impactful |
| First appeared | When Kelet first detected this pattern |
| Prompt Patch | Proposed change to your agent’s system prompt |
Prompt Patches
Section titled “Prompt Patches”A Prompt Patch is a fast, single-shot proposed edit to your agent’s system prompt that addresses the root cause. Generated immediately by an LLM from the Issue’s context.
Apply it as-is, customize it, or ignore it.
For a validated fix — one tested against your real session data using an evolutionary search — run GEPA Optimization from the dropdown. Slower, but comes with a measurable quality delta. See GEPA Optimization.
Actions
Section titled “Actions”Each Issue card has two action buttons:
- Fix ready badge — indicates a Prompt Patch is available and ready to apply.
- Prompt Patch (split button) — view and apply the suggested fix. The dropdown also exposes GEPA Optimization ( re-run the evolutionary process), Mark as Resolved, and future options (disabled for now).
- Not an issue — mark as false positive; removes the card from the Open view.
- Open — active Issues that haven’t been resolved or dismissed
- Resolved — Issues where the fix has been deployed
How to use Issues
Section titled “How to use Issues”- Go to Issues in the console
- Filter by agent using the chips at the top
- Sort by Impact — highest session count = most impact
- Read the description — is this a real problem you recognize?
- Apply or dismiss
Issues improve over time as more sessions accumulate. A pattern seen in 3 sessions is a hint; a pattern seen in 50 sessions is a root cause.