Errors & plan validation
Two adjacent post-session commands: kcap errors finds where things went wrong, kcap validate-plan confirms the agent finished what it planned. Both work on any session, the active one or a past one.
kcap errors
Section titled “kcap errors”Scan a session for tool-call errors — failed bash commands, file read/write errors, agent failures.
kcap errors <sessionId> # one sessionkcap errors <meta-session-slug> # meta session (full chain by slug)kcap errors --chain <sessionId> # full continuation chainOutput is grouped by tool with a short description of each failure. Useful for:
- Post-session review: spot recurring mistakes and update project instructions.
- Debugging a stuck agent: see whether it kept retrying the same failing operation.
- Auditing autonomy: which destructive commands the agent ran, and which were rejected.
With the plugin installed, the skill is invoked as /kcap:errors in Claude Code; in Codex and Cursor it’s the kcap-errors skill (description-matched, so the agent picks it up from a natural question — you don’t normally type the name).
Or ask naturally:
Show me the failed tool calls from the last session.kcap validate-plan
Section titled “kcap validate-plan”Verify every item in a session’s plan was completed.
kcap validate-plan <sessionId>The command reads the plan (extracted from the agent’s tool calls — Claude Code’s TodoWrite, or a markdown plan committed during the session) and checks each item against what actually happened. Output is a list of completed / pending / unverified items.
Inside the agent: /kcap:validate-plan in Claude Code, or the kcap-validate-plan skill in Codex and Cursor.
Or:
Did I finish everything in the plan? Check what's left to do.This is most useful at the end of a multi-step session, before claiming a task is done.
Related
Section titled “Related”- Session recap — the narrative summary.
- Evaluations — structured scoring across 13 quality dimensions, including a dedicated “repeated failed attempts” judge.