Post

As @bizza.pizza would put it: tapes "is long term care for your agent sessions". This is how we build the agentic platforms of the future with durable audit trails, memory, secure workflows, infrastructure, and strong loopback capabilities.

How's it work? Tapes has a number of components that enable it to have huge scale: * a storage driver (sqlite locally by default) * an LLM provider (ollama locally by default) * an embedding provider (ollama locally by default) * a vector store driver (sqlite-vec by default)

$ tapes serve brings up 1) the proxy and 2) the api server. The proxy connects to your configured LLM provider and transparently captures events and messages. The API server makes commands like "search" and "checkout" work

$ tapes chat is our experimental chat client: this lets you see the full end to end experience since it uses the proxy by default and loads the point-in-conversation checkout state.

$ tapes search "query" lets you search back on previous conversation threads and sessions: since we use content addressing, you'll see the hash for that point in the conversation turn.

$ tapes checkout <hash> lets you do context check-pointing and retry. Using a hash from the session graph, you'll be able to then use "$ tapes chat" to time travel to a point-in-conversation and retry it.