Traces now reads sessions from three more coding agents: Amp, Cline, and GitHub Copilot.
Each adapter reads the agent's own on-disk session data and normalizes it into the same trace structure as every other agent, so these sessions are shareable and resumable like any other trace.
Amp's durable unit is a thread (T-*) and one Amp thread maps to one trace. The adapter discovers threads from Amp's local logs and history (~/.cache/amp/logs/threads/, ~/.local/share/amp/history.jsonl), and when local content isn't enough it falls back to the Amp CLI (amp threads list/ amp threads export) to pull full thread content. Resume works through amp threads continue <id>.
Cline stores task conversations under ~/.cline/ (plus its VS Code extension storage), and the adapter reads them from both the current data/sessions/ layout and legacy task-history locations. It captures user/assistant messages, thinking, tool calls and results, links subagent sessions back to their lead session, and even surfaces Cline's kanban board summaries. Resume opens the session in Cline's TUI (--id <id> --tui).
The Copilot adapter reads both Copilot CLI sessions (~/.copilot/session-state/<id>/events.jsonl) and VS Code Copilot Chat sessions. It parses the JSONL event stream into user messages, thinking (reasoningText), tool calls/results, and errors, and links spawned subagents to their parent session. CLI sessions resume via copilot --resume <id>; VS Code Chat sessions can be shared but not resumed through the CLI.
Update your CLI, then run traces share to publish a sesion or traces setup to connect these agents to your git commits.