Featured
Your agent charged the card twice: making tool calls replay-safe
Why a crash mid-node re-runs tools that already fired, why the usual fixes fall short, and how 10xGraph's tool ledger and versioned writes close the gap.
10xGraph blog
Engineering notes
Engineering notes from the 10xGraph team on production AI agents: replay-safe tools, two-tier memory, auth, deployment and release news.
The blog has three kinds of posts. Tutorials build one real use case from an empty folder, with working code that was run before it was published. Engineering notes explain how 10xGraph behaves when things go wrong: a process killed mid-tool, two runs on one thread, a hung node, a stale cache. Release posts say what changed in a version and how to upgrade.
It is written for Python developers who are moving an agent from a demo to a service other people depend on, and for the platform engineers who run it. Every version is listed in the changelog. For reference material, use the docs.
Agentflow is now 10xGraph
Agentflow is now 10xGraph. Why we renamed it, what the framework is, what stays the same in your code, what changes in package names, and the honest gaps.
Hot and cold agent memory: why 10xGraph puts Redis in front of Postgres
How PgCheckpointer splits agent state between a Redis hot cache and versioned Postgres history, keeps them consistent, and behaves when either one fails.