New Adapter: Kimi Code

Traces CLI now supports Kimi Code, the coding harness from Moonshot AI. Your Kimi Code sessions now show up alongside every other agent in Traces.

How Traces reads Kimi Code

Kimi Code stores every session under ~/.kimi-code/ (overridable with KIMI_CODE_HOME), with each session living in sessions/<workdir>/<session-id>/. Traces reads that on-disk data directly.

Each session directly holds a state.json (title, working directory, subagent map) and per-agent wire.jsonl event logs under agents/main/wire.jsonl. Traces trates a directory as a valid session only when both files are present. A session_index.jsonl at the root gives traces a fast list of session, and Traces falls back to scanning the filestystem when the index is missing.

Kimi's wire.jsonl is a "wire protocol" stream of events keyed by type, and Traces normalizes them into a common trace shape:

• Full Turns. User prompts (turn.prompt), assistant thinking and text (content.part with think/text), tool calls (tool.call), and results (tool.result) each map to their own trace event.
• Tool failures. A tool result is marked as an error when Kimi reports error or isError in the results payload.
• Model. Traces picks up the model kimi used (e.g. kimi-code/k3) from congig.updates/llm.request events.

What you can do now

• Share Kimi Code sessions. Run traces share --agent kimi to publish a session. Traces resolves the right one from your working directory or you can pick one by ID. Subagent traces can be shared invidually via --list.
• Resume sessions. Traces hands the session ID back to Kimi via kimi -- session <id> resuming a subagent trace targets its parent session.
• **Connect to git commits. Traces installs hooks into ~/.kimi-code/config.toml(SessionStart,UserPromptSubmit, Stop, SessionEnd, so sessions get linked to your commits automatically).

Get started

1. Update your CLI to v0.6.12.
2. Run traces setup to install the Kimi hooks and connect sessions to your commits,
3. Run traces share to publish a session and get a link.