v0.0.13 - Full Signal

tokenuse v0.0.13 - Full Signal

tokenuse 0.0.13, named Full Signal, makes Copilot AI-credit limits useful at a glance and restores the shell and MCP activity hidden inside newer Codex Desktop orchestration calls.

Highlights

• Copilot Usage rows now show exact AI credits used, remaining, and total alongside the percentage gauge, reset time, normalized plan name, and additional-usage status in both the TUI and desktop app.
• Copilot quota sync can reuse an authenticated GitHub CLI session when the Copilot configuration does not contain a token, while preserving GitHub's fractional remaining-credit values and current plan SKUs.
• Newer Codex Desktop exec wrappers are decoded so their nested shell commands and MCP calls populate the Core Tools, Shell Commands, and MCP Servers panels.
• Existing Copilot limit sidecars and Codex session archives are reparsed once, updating the new metadata without repricing historical calls.
• Codex usage deltas and model labels are more accurate: repeated cumulative token snapshots no longer inflate totals, and complete GPT model identities such as GPT-5.6 Sol are retained.

Copilot AI-credit Detail

GitHub's user payload exposes an entitlement, a potentially fractional remaining balance, a plan SKU, the reset date, and whether overage is permitted. The Copilot adapter now retains all of those fields in normalized limit snapshots. Shared Usage data derives exact credits used from entitlement minus remaining balance, while the TUI and desktop renderers display that figure next to the gauge and show remaining over total in the balance column.

Plan SKUs such as monthly_subscriber_quota are normalized to product names such as Copilot Pro. Explicit legacy billing flags still take precedence over the observation date, so annual plans that have not switched to AI-credit billing keep their legacy wording. When no Copilot token is present in local Copilot configuration, manual quota sync falls back to gh auth token.

The Copilot limit-source fingerprint has a one-time schema discriminator. This causes unchanged sidecars archived by an older build to pass through the upgraded parser without invalidating Copilot transcript or session sources. If the enriched and legacy snapshots share an observation timestamp, the later archive row wins deterministically.

Codex Tool Activity

Newer Codex Desktop rollouts store a custom_tool_call named exec whose input is JavaScript. The useful calls are nested inside that script as invocations such as tools.exec_command(...) and tools.mcp__codebase_memory_mcp__search_graph(...). The Codex adapter now treats the outer wrapper as transparent, scans executable JavaScript while ignoring strings and comments, records each nested tool, and extracts shell command strings for the existing command splitter.

A versioned Codex source fingerprint reparses existing rollouts once. Duplicate archive rows refresh only their tool and command metadata, preserving the original import-time cost. Direct legacy exec_command calls and namespaced MCP calls continue through their existing parser paths.

Codex Accuracy

Codex usage parsing now prefers deltas between cumulative total_token_usage snapshots. Repeated snapshots with unchanged totals no longer emit extra calls or leak buffered tool activity into a later turn. Model display labels preserve the complete GPT identifier, including variant suffixes, instead of collapsing new models into a generic GPT-5 row.

Notes

• Local usage analysis remains local-only. Network calls are limited to explicit Config-page downloads, opt-in quota sync actions, local CLI advice generation selected by the user, or maintainer refresh and release paths.
• The release tag should be v0.0.13 and must match the root Cargo package, desktop Cargo package, desktop package.json, and Tauri config versions.

What's Changed

• fix(codex): prevent duplicate token snapshot overcount by @Duncanxyz in #2

New Contributors

• @Duncanxyz made their first contribution in #2

Full Changelog: v0.0.12...v0.0.13

What's Changed

• fix(codex): prevent duplicate token snapshot overcount by @Duncanxyz in #2

New Contributors

• @Duncanxyz made their first contribution in #2

Full Changelog: v0.0.12...v0.0.13