Tracing for opencode records each turn as a trace, with the model calls and tool calls it made nested beneath it. opencode installs as a plugin rather than as hook entries in a config file, and its trace shape differs from the hook-based tools.

​
Install

On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, and copies a plugin file to ~/.config/opencode/plugin/atatus-tracing.ts.
opencode discovers plugins in that directory automatically, so there is no config file to edit and no opencode.json change required. Installing the plugin file is the whole registration step.

​
What gets captured

opencode produces a three-level tree, with the model call as its own span rather than merged into the turn:
This differs from the hook-based tools, where the turn itself is the model call. In opencode traces, look for token counts and cost on the LLM span rather than on Turn.
One trace covers one turn, defined as a prompt through to the session going idle.

​
Where things live

Two lifecycle events are forwarded: message.updated when an assistant message completes, and session.idle to close the turn. Spans are sent straight from the plugin, so there is no separate collector or buffer service to run.

​
Uninstall

This deletes ~/.config/opencode/plugin/atatus-tracing.ts. Because registration is the presence of that file, removing it is all that is needed. See Uninstall for the full-wipe option.