AgentTrace: Graph-Based Memory for AI Agent RunsAgentTrace: Graph-Based Memory for AI Agent Runs
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
An AI agent fails halfway through a job. What should it remember when it tries again?
That question led me to build AgentTrace, a Python and FalkorDB project for keeping track of agent runs. It records task progress and decisions in a graph so you can inspect what happened and see where a run stopped. That’s especially useful when several agents share a workflow.
When you debug an agent run, what do you look for first: the failed step, the input that caused it, or the decision that sent it down that path?
Maksim's avatar
IDM logo
First thing I look for is the decision, not the failed step. The failed step tells you what broke, the decision tells you why the agent was there at all, and in my CLI bots most incidents are a wrong branch, not a broken call. Two things I would want in the graph: the exact...
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started