Traces now supports OpenClaw. Install Traces CLI on the same machine as your OpenClaw gateway, run traces setup, and you can share any OpenClaw conversation to traces.
Most agents traces support run in a terminal or an IDE. OpenClaw is a gateway, which means it fields mssages from chat channels and routes them to a coding agent, so a session can start with something as casual as "Yo what's up" from a chat app. Traces handles that: the adapter recognizes and strips OpenClaw's per-message gateway prelude (the Conversation info, Sender, and Delivery untrusted metadata blocks) so your trace title and message read as the actual conversation not the routing envelope.
OpenClaw stores each session as a flat .jsonl transcript on disk under ~/.openclaw/agents/<profile>/sessions/, with a sessions.json index per profile. Traces reads that data directly.
Because OpenClaw runs multiple agent profiles (for example main and main-openai), Traces discovers sessions across every profile and sorts them by most recently updated.
From each transcript, the adapter reconstructs the full turn structure:
durationMS/tookMs.The adapter can watch a session file and stream new events as they land, so an in-progress OpenClaw conversation shows up live rather than only after it finishes.
traces setup to install the OpenClaw share skill, then ask to "share to traces" and get a link back. The skill runs traces share --agent openclaw for you.traces setup to install the share skill.