| Term | Meaning |
|---|---|
| Project | Holds one app's traces, issues, connections, and fixes. |
| Agent's job | What your agent should do, the rules it follows, and what a good answer looks like. Change it in Settings. |
| Trace | A record of one request, including model calls, tool calls, and results. |
| Issue | A likely bug, shown with the traces where it happened and what should have happened instead. |
| Occurrence | One time an issue happened, in one trace. |
| Reported fix | A change you shipped to production to fix an issue. |
Kensa talks about two agents. Your app's agent is the one Kensa watches. Your coding agent (such as Claude Code) looks into issues and reports fixes.
One issue can happen many times, and one trace can have more than one issue. For example, “Refund approved after the deadline” is one issue. If it happened in three requests, that's three occurrences.
Suggested validation checks are tests you or your coding agent can run to assess the fix. See Issues for what each issue status means.