Tracing for the Kiro CLI records each prompt as a trace, with the tools it invoked nested beneath it. Kiro reports its usage differently from the other supported tools, which this page explains.

​
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 registers hooks in a Kiro agent config at ~/.kiro/agents/atatus-traced.json. Add --with-skills to also link the manage-kiro-tracing skill into the current directory.

​
Kiro traces a specific agent

Kiro scopes hooks to an agent rather than to your whole account, so tracing applies to the agent the installer creates. The default agent name is atatus-traced.
If you keep using your previous default agent, nothing is traced. The installer offers to run kiro-cli agent set-default atatus-traced for you. Accept it, or set the default yourself, or pass the agent explicitly each time you start Kiro.
To set the default agent later:

​
What gets captured

​
Credits rather than tokens

Kiro bills in credits, not tokens, so its traces report cost differently from the other tools:
  • Cost is reported in credits, as Kiro reports it.
  • Token counts appear only when Kiro includes them, which is not on every turn.
Turns with no token counts are expected for Kiro, and they do not mean tracing is broken. Compare Kiro spend against Kiro’s own credit reporting rather than against the token totals you see for other tools.

​
Where things live

Five hook events are registered: agentSpawn, userPromptSubmit, preToolUse, postToolUse, and stop.

​
Uninstall

This removes the hooks from the agent config. If you changed your default agent to atatus-traced, set it back to the one you were using before:
See Uninstall for the full-wipe option.