cargo-diagnostics
Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, draw the graph it executed with the failing step marked, sweep a batch or play for errors grouped by root cause, and attribute credit spend down to the node and the provider. Triggers: "why did this fai
as observed 2026-10-18T21:45:32.509Z- Identifier
cargo-diagnostics- Source
- ClawHub
- Version observed
- 1.5.0
- Source repository
- not published
- Repository observation
- No source repository listed
- First observed here
- 2026-08-28T22:54:40.332Z
- Observations recorded
- 3
- Installs (reported upstream)
- 1
- Weekly downloads (upstream)
- 1,241
- Declared license
- MIT-0
Observation history
2026-10-18T21:45:32.509Z
Fields that differed: license changelog description latestVersion
| Field | Before | After |
|---|---|---|
license |
null | "MIT-0" |
changelog |
"cargo-diagnostics 1.4.0\n\n- Adds explicit documentation of execution charge (0.01 credits per node execution) in cost attribution for play credit optimization.\n- Updates referen | "cargo-diagnostics 1.5.0\n\n- Updated documentation to clarify orchestration run list behavior without `--workflow-uuid` and note necessary usage of `--created-after` with a 30-day |
description |
"Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, draw the graph it executed with the failing step marked, sweep a batch or play for err | null |
latestVersion |
"1.4.0" | "1.5.0" |
2026-09-02T06:49:02.991Z
Fields that differed: changelog latestVersion
| Field | Before | After |
|---|---|---|
changelog |
"cargo-diagnostics v1.3.0\n\n- Adds support for drawing and interpreting execution graphs, clarifying run routing and skipped steps.\n- Expands triggers to cover branch logic issue | "cargo-diagnostics 1.4.0\n\n- Adds explicit documentation of execution charge (0.01 credits per node execution) in cost attribution for play credit optimization.\n- Updates referen |
latestVersion |
"1.3.0" | "1.4.0" |
Correction
If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.