session-steward 0.7.0 → 0.8.0

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [0.8.0] - 2026-08-23
+
+### Added
+
+- Session details now show how many tokens a Codex or Claude session used, with clear breakdowns for input, cache use, output, reasoning, models, and inherited work in forked sessions.
+- The same token breakdown is available in the terminal with `--tokens`.
+
 ## [0.7.0] - 2026-08-20
 
 ### Added
@@ -123,6 +130,7 @@
 - Support for custom Codex home folders and a saved folder preference.
 - Streaming and bounded-memory discovery for large session collections and transcripts.
 
+[0.8.0]: https://github.com/mallikcheripally/session-steward/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/mallikcheripally/session-steward/compare/v0.6.0...v0.7.0
 [0.6.0]: https://github.com/mallikcheripally/session-steward/compare/v0.5.2...v0.6.0
 [0.5.2]: https://github.com/mallikcheripally/session-steward/compare/v0.5.1...v0.5.2

package/README.md

@@ -21,6 +21,7 @@ Session Steward makes session cleanup safer by finding those records, showing wh
 - Filter active or archived sessions by workspace, name, or session ID.
 - Inspect session details and affected records before deletion.
 - Read a session timeline of what you asked, what changed, and which commands ran.
+- See how many tokens a session used, split into fresh input, cached input, cache writes, and output.
 - Choose standard or thorough cleanup.
 - Use custom Codex or Claude home folders across browser and terminal sessions.
 
@@ -165,6 +166,20 @@ With `--json`, each session carries its own `events`, plus a `coverage` summary
 session-steward-cli --json --limit 5 --events
 ```
 
+Use `--tokens` to count what a session spent. The total is split into fresh input, cached input, cache writes, and output, with reasoning reported as a share of output where the provider records it:
+
+```bash
+session-steward-cli --tokens
+```
+
+In the interactive list, `tokens` toggles the same breakdown into `inspect`. With `--json`, each session carries a `tokens` object:
+
+```bash
+session-steward-cli --json --limit 5 --tokens
+```
+
+Cached input usually dominates, because the whole conversation is re-sent on every turn. A forked session reports its own work separately from the tokens it inherited from the session it branched from, so the two are never added together.
+
 The interactive terminal accepts the same filters:
 
 ```text
@@ -176,6 +191,7 @@ archive archived
 workspace /path/to/project
 internals
 supporting
+tokens
 cleanup standard
 cleanup thorough
 overview

package/bin/session-steward-cli.mjs

@@ -29,6 +29,9 @@ const { values } = parseArgs({
     events: {
       type: "boolean",
     },
+    tokens: {
+      type: "boolean",
+    },
     "events-limit": {
       type: "string",
     },
@@ -116,6 +119,7 @@ async function main() {
     providerId,
     search: values.search ?? "",
     sort: values.sort ?? "updated",
+    tokens: values.tokens ?? false,
     workspace: values.workspace,
   });
 }