Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From nika
Reads a Nika run's flight recorder — shows verdict, root-cause task, integrity check, and resume command if paused.
How this command is triggered — by the user, by Claude, or both
Slash command
/nika:trace trace-or-workflowThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Read the journal, not a memory of the terminal — `.nika/traces/` is the only truth about what a run did. Target: `$ARGUMENTS` (no argument? `nika trace ls` and take the `★` newest — say which one you picked). 1. `nika trace show <trace>` — the verdict card. Then `nika trace outputs <trace>` — per-task verb · duration · tokens · bounded preview. The FIRST red task is the root cause; downstream reds are fallout. 2. `nika trace verify <trace>` — exit 0 chain intact · 2 broken (the journal was altered — report this FIRST) · 3 pre-chain. 3. Report in this order: - **Verdict** — ...
Read the journal, not a memory of the terminal — .nika/traces/ is
the only truth about what a run did.
Target: $ARGUMENTS (no argument? nika trace ls and take the ★
newest — say which one you picked).
nika trace show <trace> — the verdict card. Then
nika trace outputs <trace> — per-task verb · duration · tokens ·
bounded preview. The FIRST red task is the root cause; downstream
reds are fallout.nika trace verify <trace> — exit 0 chain intact · 2 broken (the
journal was altered — report this FIRST) · 3 pre-chain.<task> · paused on
<prompt>.nika explain NIKA-XXXX (fold the teaching in, never
paraphrase from memory).nika run <file> --resume <trace> --answer <task>=<value>
(confirm gates take booleans) · fixed upstream:
nika run <file> --from <task-id> · one flaky task:
nika run <file> --task <task-id>.nika trace replay re-renders
(never re-executes) if the human wants to watch it again; the run
line is theirs. Dashboards? nika trace export <trace> emits
OTLP/JSON lines any OTel viewer reads.npx claudepluginhub supernovae-st/nika-agents --plugin nika2plugins reuse this command
First indexed Jul 14, 2026
/traceReads a Nika run's flight recorder — shows verdict, root-cause task, integrity check, and resume command if paused.
/traceRenders the reasoning trace for a task — file reads, tool calls, output claims, and decisions. Surfaces potential hallucinations by flagging ungrounded claims.
/ng-traceCaptures agent run traces for debugging, auditing, and cost review. Produces trace rows, decision-point records, token/speed summary, and links to verification claims.
/statusShows the current algokiller session state, reporting bound trace, output directory, hypothesis ledger summary, and artifacts written with recommendations.
/trace-taskRetrieves and analyzes full session history (Conductor + Agent) for a task ID from JSONL output, summarizing timeline, errors, judgments, and deliverables.