Install and run TTDash
TTDash is a local-first dashboard and CLI for toktrack usage data. The fastest path is to run the latest published package directly.
Requirements
Section titled “Requirements”- Node.js 20 or newer for npm and npx installations
- a modern browser
- npm or Bun when auto-import needs a package-runner fallback
- Typst only when you want PDF export
- Docker with Compose v2 only for container deployments
Run without a global install
Section titled “Run without a global install”Use either package runner:
npx --yes @roastcodes/ttdash@latestbunx @roastcodes/ttdash@latestTTDash starts on http://127.0.0.1:3000. If that port is occupied, it tries the requested port and up to 100 following ports, then prints the selected URL.
Install globally
Section titled “Install globally”Install the ttdash command when you use it regularly:
npm install --global @roastcodes/ttdashttdashbun add --global @roastcodes/ttdashttdashConfirm the executable without starting the server:
ttdash --helpFirst launch
Section titled “First launch”- Start TTDash.
- Let it open the generated local authentication URL, or copy the Local Auth URL from the terminal when browser opening is disabled.
- Select Auto import to run the TTDash-pinned toktrack version, or choose Upload and select compatible JSON.
- Use the filter bar to choose a period, provider, model, and daily/monthly/yearly aggregation.
- Open Settings to save default filters, section order, theme, language, and motion preferences.
The local server generates a fresh bootstrap token for each start, exchanges it for an HttpOnly browser cookie, and removes it from the address. You do not need to configure a password for ordinary loopback use.
Common starts
Section titled “Common starts”# Choose the first port to try.ttdash --port 3010
# Do not open a browser.ttdash --no-open
# Import toktrack data once during startup.ttdash --auto-load
# Run as a managed background instance.ttdash --background
# Stop a managed background instance.ttdash stopFlags can be combined:
ttdash --background --port 3010 --auto-loadSee Configuration and CLI for every supported option, environment variable, and storage location.
Keep enough source history
Section titled “Keep enough source history”toktrack can only report usage that still exists in the underlying tools’ local history. For example, Claude Code removes older sessions after its configured retention period. If you need a longer history, set an appropriate cleanupPeriodDays in ~/.claude/settings.json before old sessions are removed:
{ "cleanupPeriodDays": 365}Choose a retention value that matches your own storage and privacy requirements.
Next steps
Section titled “Next steps”- Import data and understand replacement versus merge behavior.
- Learn the dashboard and filter workflow.
- Configure remote access only when loopback access is not enough.