The recorder lands.

On October 26, 2026, the first pieces of Wake’s open source recorder landed: a Python SDK, a collector that signs what the SDK sends, and a signed log you host yourself. Together they take an agent’s work from its own process to a record it can’t rewrite.

The SDK

The Python SDK records a LangGraph agent’s work as events: OpenTelemetry spans, with Wake’s own fields for which agent acted and what it did. It never signs anything, and holds no key. It sends its events, unsigned, to the collector.

The collector

The collector is an OpenTelemetry Collector with a processor of Wake’s. It’s the first hop outside the agent’s process, so it’s where the SDK’s events are signed, as they arrive. Why there. An exporter then appends each one to the log.

The signed log

The log is append-only, built on Trillian Tessera, and kept wherever you run it: Wake doesn’t have to host it. Its checkpoints are signed, and anyone can check it, with the open source wake-log or any tool that reads Tessera’s tlog-tiles format, without trusting Wake.

What came next

A day later, on October 27, the proxy’s MCP capture landed, recording the MCP calls agents make through agentgateway. So did the reference fleet: agents on three frameworks and a poisoned web page, which became the recorder’s end-to-end test.

The recorder is open source, under Apache 2.0, and the reference fleet runs the whole of it on your machine.