New Adapter: OpenClaw

Mar 26, 2026

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.

Why OpenClaw is different

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.

How Traces reads OpenClaw

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:

User messages, agent thinking, agent text, tool calls, and tool results. Parsed in order into a normalized trace.
Per-message token input. Input, output, cache-read, cache-write, and reasoning tokens are arried onto the events that report them.
Accurate tool timing. Durations come from the tool's own durationMS/tookMs.

Live sessions, in real time

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.

What you can do

Share from any channel. Run 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.
Attach the conversation to a PR. Message your agent through a chat channel, have it open a PR, and share that session to Traces so the PR carries the conversation that produced it.

Get started

Install the Traces CLI on the same machine as your OpenClaw gateway.
Run traces setup to install the share skill.
Ask to "share to traces" from tany channel to publish a session and get a link.

Why OpenClaw is different

How Traces reads OpenClaw

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:

User messages, agent thinking, agent text, tool calls, and tool results. Parsed in order into a normalized trace.

Per-message token input. Input, output, cache-read, cache-write, and reasoning tokens are arried onto the events that report them.

Accurate tool timing. Durations come from the tool's own durationMS/tookMs.

What you can do

Share from any channel. Run 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.

Attach the conversation to a PR. Message your agent through a chat channel, have it open a PR, and share that session to Traces so the PR carries the conversation that produced it.