Who it is forA reviewer or team lead who needs to confirm that an agent's summary of its work is backed by real tool calls and file changes.
The problemAn agent's final message describes what it believes happened, which may not match the commands and writes that actually ran.
The outcomeYou can locate the completion audit outcome in the turn's log entry and confirm the claims against the filesystem.
What you need first
- A CluxMate install (install steps are not in the README excerpt provided, so follow the README's install section)
- An OpenAI-compatible API endpoint, its base_url, and an API key
- A git repository for the project you want the agent to work on
Steps
- Run a task in the TUI with
cluxmate, or in one shot withcluxmate -p "<prompt>". (inferred, check the README) - Open the session's append-only
.jsonlevent log. - Find the
turn/endevent for the turn and read itsreason.completion_auditfield. - For each claim that files changed, check the filesystem and the
git diffyourself. (inferred, check the README)
Prompt for your agent
Use the CluxMate repo (r1c7/CluxMate) to run the task <task> and then inspect its session .jsonl log. Expected output: the turn/end entry with completion_audit and a list of claims checked. Verify that every claimed file change appears in git diff.
Caveat. The README excerpt describes the log events but not where session files are stored, so locate the session directory from the full README or the app before starting.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for r1c7/CluxMate and "Audit an agent's claims against its session log"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer