mirror of https://github.com/rtk-ai/rtk.git synced 2026-09-19 07:33:17 +08:00

Files

T

History

David Alecrim f68fa0087c fix(ccusage): add --yes flag and warn when falling back to npx

Fixes silent hang when ccusage is not installed globally. npx prompts
for confirmation before installing the package, blocking the subprocess
indefinitely. Adding --yes auto-confirms and the info message sets user
expectations.

Fixes rtk-ai/rtk#1226

2026-04-11 12:43:54 -03:00

cc_economics.rs

fix(cmds): shared cmd execution flow + clean & update docs

2026-03-29 13:40:10 +02:00

ccusage.rs

fix(ccusage): add --yes flag and warn when falling back to npx

2026-04-11 12:43:54 -03:00

gain.rs

fix(gain): convert history timestamps from UTC to local timezone

2026-03-27 14:43:34 +07:00

mod.rs

chore(refacto-codebase): Folders + Technical docs

2026-03-24 22:14:35 +01:00

README.md

fix(docs): clean some docs + disclaimer

2026-04-02 21:33:38 +02:00

session_cmd.rs

fix(refacto): conflict w/ dev

2026-03-25 19:56:53 +01:00

README.md

Analytics

See also docs/contributing/TECHNICAL.md for the full architecture overview

Scope

Read-only dashboards over the tracking database. Queries token savings, correlates with external spending data, and surfaces adoption metrics. Never modifies the tracking DB.

Owns: rtk gain (savings dashboard), rtk cc-economics (cost reduction), rtk session (adoption analysis), and Claude Code usage data parsing.

Does not own: recording token savings (that's core/tracking called by cmds/), or command filtering itself (that's cmds/).

Boundary rule: if a new module writes to the DB, it belongs in core/ or cmds/, not here. Tool-specific analytics (like cc_economics reading Claude Code data) are fine — the boundary is "read-only presentation", not "tool-agnostic".

Purpose

Token savings analytics, economic modeling, and adoption metrics.

These modules read from the SQLite tracking database to produce dashboards, spending estimates, and session-level adoption reports.

Adding New Functionality

To add a new analytics view: (1) create a new *_cmd.rs file in this directory, (2) query core/tracking for the metrics you need using the existing TrackingDb API, (3) register the command in main.rs under the Commands enum, and (4) add #[cfg(test)] unit tests with sample tracking data. Analytics modules should be read-only against the tracking database and never modify it.