Skip to main content

Crate usage

Crate usage 

Source
Expand description

Session usage (ultron/usage-cli.ts): a session file read into its usage log (log), the session report built from it (report, with the cell statistics of stats) and the report as text (text). ultron usage, the TUI’s /usage and ultron mcp’s usage.report inspection all show this report.

Modules§

log
A native session file read for the session report without opening the session (ultron/session-log.ts): a digest of each entry (who wrote it and what it used, never its text), the latest values of the namespaces the report reads, and every operation’s lane and result.
report
“What did this session do?” (ultron/session-report.ts): turns, cells, depth (frames, subagents, workflows, jobs), tokens and cost per lane kind and model, guardrails and memory decisions, from a session file’s digest. A number the session did not keep is null and named in unrecorded; it is never reported as zero.
stats
The parts of ultron/session-stats.ts the report reads: which REPL APIs a cell names, which steer a message is, and the stored runtime counters (ultron.module/stats).
text
The session report as text (ultron/session-report-text.ts): the full report of one session and the one-line-per-session table. A number the session did not keep prints as not recorded (n/r in the table), and a cost nobody reported as unknown: neither is ever printed as zero. Plain style only (the CLI prints no color).

Functions§

session_report
The session report of the session file path as /usage builds it: providers (those on a subscription login, subscriptionProviders) are priced as notional.