Skip to main content
Replay reconstructs what the agent was thinking at each turn: the system prompt, the message history as it grew, and every tool call with its arguments and result. It is opt-in, and nothing is captured until you ask for it.

​
Capture

A snapshot is written at each completed message, rate-capped to one per second, and at each resolved tool call, which bypasses the cap because tool calls are rare and are the most useful thing in a replay.
Off by default on purpose. A snapshot is a larger disclosure than a transcript: it carries your system prompt and whatever payloads your tools handle, not just what the caller said. Turn it on deliberately, and see replay storage costs before leaving it on across a fleet.

​
What is not captured

STT chunks, LLM tokens, and TTS frames. Those are per-chunk, per-token, and per-frame, and capturing them would mean sitting inside the media and inference streams. VoiceGateway does not do that, which is the same reason it adds no latency on happy-path calls.

​
View a replay

voicegw replay prints the dashboard URL for a session and exits. It renders nothing in the terminal.
The daemon must already be running before the printed URL resolves. Start it with voicegw serve. voicegw dashboard only opens a browser; it starts nothing.