tine show
Display the full step hierarchy of a run as a pretty-printed tree in your terminal. Each step shows its kind, label, duration, and cost.
Usage
Terminal
tine show <run_id>Identifying Runs
The <run_id> argument accepts either a run ID or a file path. When given a run ID (or a unique prefix of one), the CLI searches the .tine_runs/ directory for a matching file. You can also pass a direct path to any .tine file.
Terminal
# By run ID (prefix match)
tine show a3f8c1d2
# By full .tine file path
tine show .tine_runs/run_a3f8c1d2.tine
# By relative or absolute path
tine show ./my_runs/research.tineOutput Format
The output begins with a summary header showing the run ID, status, total step count, aggregate cost, total duration, and model. Below that, every step is printed in a tree layout with the following columns:
- Kind: The step type in brackets —
[think],[tool],[model],[done], or[error]. - Label: A human-readable description of what the step did.
- Duration: Wall-clock time for the step in seconds.
- Cost:Token cost for the step in USD (zero for tool calls that don't invoke a model).
Example Output
Terminal
Run: run_a3f8c1d2
Status: completed | Steps: 12 | Cost: $0.0341 | Duration: 18.7s
Model: claude-sonnet-4-20250514
├─ [think] Planning research approach 0.8s $0.0012
├─ [tool] search("solid-state battery 2026") 1.2s $0.0000
├─ [model] Analyzing 8 search results 2.1s $0.0058
├─ [tool] fetch("https://example.com/review") 0.9s $0.0000
├─ [tool] fetch("https://example.com/update") 0.7s $0.0000
├─ [model] Cross-referencing sources 2.4s $0.0062
├─ [think] Evaluating conflicting claims 1.1s $0.0018
├─ [model] Synthesizing findings 3.2s $0.0089
├─ [tool] fetch("https://example.com/specs") 0.8s $0.0000
├─ [model] Final synthesis 2.9s $0.0074
├─ [tool] write("battery_report.md") 0.3s $0.0000
└─ [done] Report written to battery_report.md 0.0s $0.0028