Kensa reads your agent's production traces, detects issues and gives your coding agent, like Claude Code or Codex, the context to fix them. After you ship a fix, Kensa monitors whether the issue reccurs.
Think of Kensa less as an observability platform and more as a behavior monitoring tool that catches bugs, alerts you, and fixes issues in production.
Give this prompt to your coding agent:
Fetch https://kensa.sh/install and follow it.Follow the Quickstart to send your first request and explore your issues.
The core input is a trace: a record of an agent request, including captured inputs, model calls, tool calls, and outputs.
How it works
- Connect your traces.
- Tell Kensa what your agent should do. This is optional.
- Look at an issue and confirm or dismiss it.
- Give it to your coding agent to fix.
- Ship the fix and report it. Kensa watches for recurrence.
Coding agents
Kensa works with any coding agent that supports MCP, such as Claude Code, Codex, and Cursor. See Agent workflow to connect yours.