DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to trace why your agent made a bad tool call with ZizkaDB

Use ZizkaDB's causal chain, session replay and time travel to walk back from a wrong tool call to the message or context that caused it.

Short answer: Start ZizkaDB with the quickstart or the docker run command and log your agent through the SDK; then Find the suspicious event in the dashboard and open the Why? (causal) tab; from the terminal, run zizkadb why with that event's id. All steps.

Who it is forAn engineer debugging an agent that did something odd in production, such as calling the wrong tool or using stale information.

The problemFlat traces show what happened but not why, and you cannot see what the agent knew at the moment it decided.

The outcomeThe causal chain behind any event, a step by step replay of the session, and a rebuild of the agent's knowledge at any past timestamp.

What you need first

  • Docker
  • Python or TypeScript SDK for integration

Steps

  1. Start ZizkaDB with the quickstart or the docker run command and log your agent through the SDK
  2. Find the suspicious event in the dashboard and open the Why? (causal) tab
  3. From the terminal, run zizkadb why with that event's id
  4. In code, call db.why(event_id) to print the chain back to the user message
  5. Call db.at(agent, timestamp) to see exactly what the agent knew at that moment
  6. Replay the whole session event by event to find where it went wrong

Prompt for your agent

Using ZizkaDB, explain why <agent> called <tool> in session <id>: print the db.why chain for that event, rebuild what the agent knew with db.at at that time, and point to the step where the context was wrong.

Caveat. Replay and causal chains cover only what your integration logged.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for ZIZKA-AI-SL/ZizkaDB and "Trace why your agent made a bad tool call"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer