@juliantanx/aiusage 1.3.4 → 1.4.0

package/README.md

@@ -1,28 +1,12 @@
 # aiusage — AI Coding Assistant Usage Tracker
 
-**Website: [aiusage.jtanx.com](https://aiusage.jtanx.com)**
-
-Track token usage, cost, and sessions across **7 AI coding tools** — local-first, no accounts required.
-
 [![npm version](https://img.shields.io/npm/v/@juliantanx/aiusage)](https://www.npmjs.com/package/@juliantanx/aiusage)
 [![CI](https://github.com/juliantanx/aiusage/actions/workflows/test.yml/badge.svg)](https://github.com/juliantanx/aiusage/actions/workflows/test.yml)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
-[![Node.js](https://img.shields.io/badge/Node.js-20%2B-green.svg)](https://nodejs.org/)
-[![Website](https://img.shields.io/badge/Website-aiusage.jtanx.com-blue.svg)](https://aiusage.jtanx.com)
 
-English | [中文](https://github.com/juliantanx/aiusage/blob/main/README_zh.md)
-
-## Quick Start
-
-**Prerequisites:** Node.js 20 or later
-
-```bash
-npm install -g @juliantanx/aiusage
-aiusage parse
-aiusage serve
-```
+**[aiusage.jtanx.com](https://aiusage.jtanx.com)** · English | [中文](https://github.com/juliantanx/aiusage/blob/main/README_zh.md)
 
-Open `http://localhost:3847` to explore the dashboard.
+Track token usage, cost, and sessions across **22 AI coding tools** in one local dashboard. No accounts. No telemetry. No cloud required.
 
 <p align="center">
   <img src="https://raw.githubusercontent.com/juliantanx/aiusage/a527444cf87a9c1e92f1440282ed4e94f744b910/packages/site/static/screenshots/dashboard-home.png" alt="aiusage dashboard home" width="32%" />
@@ -30,559 +14,39 @@ Open `http://localhost:3847` to explore the dashboard.
   <img src="https://raw.githubusercontent.com/juliantanx/aiusage/a527444cf87a9c1e92f1440282ed4e94f744b910/packages/site/static/screenshots/sessions.png" alt="aiusage sessions dashboard" width="32%" />
 </p>
 
-> If aiusage is useful, **[star this repo](https://github.com/juliantanx/aiusage)** to help more developers discover it.
-
-`aiusage` does not run a built-in background parser. If you want automatic imports, schedule `aiusage parse` with cron or Task Scheduler.
-
-### Running in Background (PM2)
-
-`aiusage serve` runs in the foreground and stops when you close the terminal. To keep it running in the background on **Windows, macOS, and Linux**, use [PM2](https://pm2.keymetrics.io/):
-
-```bash
-# Install PM2 (one-time)
-npm install -g pm2
-
-# Start aiusage as background services (generates config + starts PM2)
-aiusage pm2-start
-
-# Set auto-start on boot (Linux / macOS: run directly; Windows: run the output command as Administrator)
-pm2 startup
-
-# Common commands
-pm2 list            # View running status
-pm2 logs            # View logs
-pm2 stop all        # Stop all services
-pm2 restart all     # Restart all services
-pm2 delete all      # Remove all services
-```
-
-<details>
-<summary>Build from source</summary>
-
-```bash
-git clone https://github.com/juliantanx/aiusage.git
-cd aiusage
-pnpm install
-pnpm build
-cd packages/cli
-npm link
-```
+## Quick Start
 
-After pulling updates, rebuild to pick up changes:
+**Prerequisites:** Node.js 20+
 
 ```bash
-pnpm build
+npm install -g @juliantanx/aiusage
+aiusage parse
+aiusage serve
 ```
 
-If you switch Node.js versions locally, recompile the `better-sqlite3` native module for the new version:
-
-```bash
-pnpm rebuild:sqlite
-```
+Open `http://localhost:3847` to explore the dashboard.
 
-> This is only needed when developing from source. Users who install via `npm install -g` do not need to do this — the module is compiled automatically during installation.
+## Supported Tools
 
-</details>
+| | | | | |
+|---|---|---|---|---|
+| `Claude Code` | `Codex` | `OpenCode` | `Cursor` | `Hermes` |
+| `Qoder` | `OpenClaw` | `KiloCode` | `Copilot` | `Gemini CLI` |
+| `Kimi Code` | `CodeBuddy` | `Kiro` | `Grok Build` | `Antigravity` |
+| `Roo Code` | `Zed` | `Goose` | `oh-my-pi` | `pi` |
+| `Craft` | `Droid` | | | |
 
 ## Why aiusage
 
-Your AI coding tools each log usage separately — different formats, different machines, no shared view. aiusage pulls it all into one local dashboard with no accounts, no telemetry, and no cloud required.
+Your AI coding tools each log usage separately — different formats, different machines, no shared view. aiusage pulls it all into one local dashboard:
 
 - **One dashboard** for tokens, cost, model mix, and tool-call activity
 - **Multi-machine sync** via GitHub, S3, or R2 — entirely optional
 - **Your data stays local** by default
 
-## Supported tools
-
-| Tool | Status |
-|------|--------|
-| Claude Code | ✅ |
-| Codex | ✅ |
-| OpenCode | ✅ |
-| Cursor | ✅ |
-| Hermes | ✅ |
-| Qoder | ✅ |
-| OpenClaw | ✅ |
-
-
-## CLI Reference
-
-### `aiusage` (default)
-
-Print a usage summary to the terminal (same as `aiusage summary`).
-
-### `aiusage parse`
-
-Import newly appended local session data from discovered source paths.
-
-| Option | Description |
-|--------|-------------|
-| `--tool <tool>` | Only parse a specific tool: `claude-code`, `codex`, `openclaw`, `opencode`, `hermes`, `qoder`, `cursor` |
-| `--progress` | Show real-time progress bar on stderr (TTY only, silent in pipes/CI) |
-
-```bash
-aiusage parse                        # Parse all tools
-aiusage parse --tool claude-code     # Only parse Claude Code logs
-aiusage parse --progress             # Show progress bar while parsing
-```
-
-### `aiusage serve`
-
-Start the local web dashboard and runtime settings controller.
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `-p, --port <port>` | Port number | `3847` |
-
-```bash
-aiusage serve             # Start on port 3847
-aiusage serve -p 8080     # Start on port 8080
-```
-
-### `aiusage summary`
-
-Print a usage summary in the terminal.
-
-| Option | Description |
-|--------|-------------|
-| `--device <id>` | Filter by device instance ID |
-| `--tool <tool>` | Filter by tool type (`claude-code`, `codex`, `openclaw`, `opencode`, `hermes`, `qoder`, `cursor`) |
-
-```bash
-aiusage summary                        # All-time summary
-aiusage summary --tool claude-code     # Single tool
-```
-
-### `aiusage status`
-
-Show version, device name, DB path, schema version, table/view counts, record count, DB size, and sync status.
-
-### `aiusage export`
-
-Export records as CSV, JSON, or NDJSON.
-
-| Option | Description | Required |
-|--------|-------------|----------|
-| `--format <format>` | Output format: `csv`, `json`, `ndjson` | Yes |
-| `-o, --output <file>` | Output file path (default: stdout) | No |
-
-```bash
-aiusage export --format csv                 # CSV to stdout
-aiusage export --format json -o report.json # JSON to file
-aiusage export --format ndjson              # NDJSON to stdout
-```
-
-### `aiusage clean`
-
-Remove old records from the local database based on age.
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `--before <duration>` | Delete data older than this duration (e.g. `30d`, `180d`) | `180d` |
-
-```bash
-aiusage clean                    # Delete records older than 180 days
-aiusage clean --before 30d       # Delete records older than 30 days
-aiusage clean --before 90d --yes # Delete records older than 90 days, skip confirm
-```
-
-### `aiusage reset`
-
-Delete all parsed records, tool calls, synced data, and the parse watermark. Source log files (`~/.claude`, `~/.codex`, etc.) are **not** affected. Use this to re-import everything from scratch.
-
-| Option | Description |
-|--------|-------------|
-| `--yes` | Skip confirmation prompt (required to execute) |
-
-```bash
-aiusage reset --yes    # Wipe all data, then run `aiusage parse` to re-import
-```
-
-### `aiusage recalc`
-
-Recalculate costs using the latest pricing data.
-
-```bash
-aiusage recalc
-```
-
-### `aiusage init`
-
-Configure a sync backend for multi-machine data aggregation.
-
-| Option | Description |
-|--------|-------------|
-| `--backend <backend>` | Sync backend: `github`, `s3`, `skip` |
-| `--repo <repo>` | GitHub repository (format: `username/repo-name`) |
-| `--token <token>` | GitHub Personal Access Token |
-| `--bucket <bucket>` | S3 bucket name |
-| `--prefix <prefix>` | S3 object prefix (default: `aiusage/`) |
-| `--endpoint <endpoint>` | S3 endpoint URL |
-| `--region <region>` | S3 region (default: `auto`) |
-| `--access-key-id <id>` | S3 access key ID |
-| `--secret-access-key <key>` | S3 secret access key |
-| `--device <alias>` | Device alias |
-
-```bash
-aiusage init --backend github --repo user/aiusage-data --token ghp_xxx
-aiusage init --backend s3 --bucket my-bucket --endpoint https://xxx.r2.cloudflarestorage.com --access-key-id AKIAxxx --secret-access-key xxx
-```
-
-### `aiusage sync`
-
-Push and pull data with the configured remote backend.
-
-```bash
-aiusage sync
-```
-
-## Web Dashboard
-
-```bash
-aiusage serve
-# Open http://localhost:3847
-```
-
-`aiusage serve` hosts the following dashboard pages:
-
-- **Home (`/`)** — live counter homepage. On first load it calls `/api/refresh`, runs one incremental local parse, then loads summary data. After that, it refreshes on the configured dashboard poll interval.
-- **Overview (`/overview`)** — totals, cost, active days, and per-tool breakdowns for Today, This Week, This Month, Last 30d, or All Time.
-- **Tokens** — token usage trends over time, with breakdown-by-type or combined total view.
-- **Cost** — cost trends with by-tool and by-model breakdowns.
-- **Models** — model share and distribution.
-- **Tool Calls** — tool call frequency and ranking.
-- **Projects** — project-level usage rollups.
-- **Sessions** — session browsing with filters and pagination.
-- **Pricing** — active model pricing reference.
-- **Settings** — configure device name, week start day, dashboard poll interval, auto-parse interval, source paths, sync backend, credentials, and local data retention without editing config files manually.
-- **Docs** — in-app documentation with CLI reference and feature guides.
-
-**Settings behavior**
-
-- **Dashboard Poll Interval** is in milliseconds and only controls the homepage refresh cycle after the initial load.
-- **Auto-Parse Interval** is in milliseconds and schedules background `aiusage parse` runs only while `aiusage serve` is running. Set `0` or leave it blank to disable it.
-- **Local Data Retention** runs periodic cleanup only while `aiusage serve` is running. Set `0` or leave it blank to keep data forever.
-- **Source path** changes take effect on the next parse.
-- **Sync backend and credential** changes take effect on the next sync.
-
----
-
-## Deployment
-
-Need multi-machine aggregation or cloud access? Choose your scenario:
-
-| Scenario | Method | Description |
-|----------|--------|-------------|
-| Multiple machines, aggregate data | [Multi-Machine Sync](#multi-machine-sync) | Sync via GitHub/S3/R2 |
-| Multiple machines + unified dashboard | [Docker Deployment](#docker-deployment) | Run a 24/7 dashboard from synced data |
-
-For single-machine usage, Quick Start is enough.
-
-### Multi-Machine Sync
-
-Use this to aggregate token usage from multiple machines into one dashboard. Works with Claude Code, Codex, OpenClaw, OpenCode, Hermes, and Qoder.
-
-**Architecture:**
-
-```
-Machine A ──┐
-Machine B ──┼──▶ GitHub / S3 / R2 (shared storage) ──▶ Any machine: aiusage summary / serve
-Machine C ──┘
-```
-
-**Step 1 — Choose a sync backend**
-
-**Option A: GitHub (recommended)**
-
-1. Create a **private** repository on GitHub (for example `aiusage-data`)
-2. Generate a [Personal Access Token](https://github.com/settings/tokens) with `repo` scope
-
-**Option B: AWS S3 / Cloudflare R2**
-
-1. Create an S3 or R2 bucket
-2. Create an IAM user or role with read/write permissions
-3. Note the access key ID, secret access key, and endpoint
-
-**Step 2 — Install and configure on each machine**
-
-On every machine that uses Claude Code, Codex, OpenClaw, OpenCode, Hermes, or Qoder:
-
-```bash
-# Install aiusage CLI
-npm install -g @juliantanx/aiusage
-
-# Configure sync backend — GitHub
-aiusage init --backend github \
-  --repo <user>/aiusage-data \
-  --token ghp_xxxxxxxxxxxxxxxxxxxx
-
-# OR configure sync backend — S3 / R2
-aiusage init --backend s3 \
-  --bucket my-aiusage-bucket \
-  --prefix aiusage/ \
-  --endpoint https://<account-id>.r2.cloudflarestorage.com \
-  --region auto \
-  --access-key-id AKIAxxxxxxxxxxxx \
-  --secret-access-key xxxxxxxxxxxxxxxxxxxxxxxxxx
-```
-
-**Step 3 — Parse and sync on each machine**
-
-```bash
-aiusage parse
-aiusage sync
-```
-
-**Step 4 — View aggregated data on any machine**
-
-```bash
-aiusage sync
-aiusage summary
-aiusage serve
-```
-
-**Automate (recommended)**
-
-```bash
-# Linux/macOS
-crontab -e
-# Add:
-*/30 * * * * /usr/local/bin/aiusage parse && /usr/local/bin/aiusage sync >> ~/.aiusage/cron.log 2>&1
-
-# Windows
-schtasks /create /tn "AiusageSync" /tr "aiusage parse && aiusage sync" /sc minute /mo 30
-```
-
-**How sync works**
-
-- Each machine has a unique `deviceInstanceId` generated on first run.
-- Each device writes to its own daily file (`{deviceInstanceId}/YYYY/MM/DD.ndjson`) in the remote backend.
-- Pull reads other devices' files into the local `synced_records` table; upload writes only this device's files.
-- Device-partitioned files avoid write conflicts, so no locking is needed.
-- Sync frequency comes from your external scheduler or manual runs; aiusage does not include a built-in sync daemon.
-- Session IDs are anonymized via `sha256(device + sessionId)`.
-
----
-
-### Docker Deployment
-
-Run the pre-built image on a server for a 24/7 dashboard. The container does **not** run any AI coding tools itself — it serves the web dashboard, can run the same runtime settings controller as `aiusage serve`, and can pull synced data from GitHub, S3, or R2.
-
-**Architecture:**
-
-```
-Machine A ──┐                           ┌── Browser: https://aiusage.your-domain.com
-Machine B ──┼──▶ GitHub / S3 / R2 ──▶ Cloud Server (Docker)
-Machine C ──┘                           └── port 3847
-```
-
-**How data flows**
-
-1. Each dev machine runs `aiusage parse && aiusage sync` to upload local usage data.
-2. The Docker container runs `aiusage sync` to pull that data into its local SQLite database.
-3. The web dashboard reads from the local database and displays aggregated stats.
-
-**Data storage in Docker**
-
-| Item | Container path | Description |
-|------|---------------|-------------|
-| Database | `/root/.aiusage/cache.db` | SQLite database with aggregated usage data |
-| Config | `/root/.aiusage/config.json` | Sync backend config, runtime settings, and credentials |
-| State | `/root/.aiusage/state.json` | Consent and sync runtime state |
-| Watermarks | `/root/.aiusage/watermark.json` | Incremental parse cursors |
-
-All data lives under `/root/.aiusage`, which is declared as a `VOLUME`. You **must** mount this volume to persist data across container restarts.
-
-**Step 1 — Pull image and run**
-
-```bash
-# Pull image
-docker pull juliantanx/aiusage
-
-# Run container (mount volume for data persistence)
-docker run -d \
-  --name aiusage \
-  -p 3847:3847 \
-  -v aiusage-data:/root/.aiusage \
-  juliantanx/aiusage
-
-# Configure sync backend
-docker exec -it aiusage aiusage init \
-  --backend github \
-  --repo <user>/aiusage-data \
-  --token ghp_xxxxxxxxxxxxxxxxxxxx
-
-# Initial data pull
-docker exec -it aiusage aiusage sync
-```
-
-> Without the `-v` flag, data is lost when the container is removed.
-
-**Step 2 — Scheduled sync**
-
-```bash
-# Install cron in container and create scheduled task
-docker exec -it aiusage bash -c "apt-get update && apt-get install -y cron"
-docker exec -it aiusage bash -c \
-  'echo "*/30 * * * * aiusage sync >> /root/.aiusage/cron.log 2>&1" | crontab -'
-docker restart aiusage
-```
-
-> Note: `parse` is not needed here unless you also mount local AI session logs into the container. In the standard deployment, only `sync` is needed to pull data from the remote backend.
-
-**Step 3 — Access**
-
-Open `http://<server-ip>:3847`.
-
-For HTTPS with a custom domain:
-
-```bash
-# Caddy (auto HTTPS, recommended)
-caddy reverse-proxy --from aiusage.your-domain.com --to localhost:3847
-
-# Or Nginx
-server {
-    listen 80;
-    server_name aiusage.your-domain.com;
-    location / {
-        proxy_pass http://127.0.0.1:3847;
-        proxy_set_header Host $host;
-        proxy_set_header X-Real-IP $remote_addr;
-    }
-}
-```
-
-**Build image yourself (optional)**
-
-A `Dockerfile` is included in the project root:
-
-```bash
-docker build -t aiusage .
-```
-
----
-
-## Data Storage
-
-| Item | Path |
-|------|------|
-| Local database | `~/.aiusage/cache.db` |
-| Config | `~/.aiusage/config.json` |
-| Sync state | `~/.aiusage/state.json` |
-| Parse watermarks | `~/.aiusage/watermark.json` |
-
-### Default Source Paths
-
-`aiusage parse` auto-discovers session logs from the following default locations:
-
-| Tool | macOS | Linux | Windows |
-|------|-------|-------|---------|
-| Claude Code | `~/.claude/projects/` | `~/.claude/projects/` | `%USERPROFILE%\.claude\projects\` |
-| Codex | `~/.codex/sessions/` | `~/.codex/sessions/` | `%USERPROFILE%\.codex\sessions\` |
-| OpenClaw | `~/.openclaw/agents/*/sessions/` | `~/.openclaw/agents/*/sessions/` | `%USERPROFILE%\.openclaw\agents\*\sessions\` |
-| OpenCode | `~/Library/Application Support/opencode/opencode.db` | `~/.local/share/opencode/opencode.db` | `%APPDATA%\opencode\opencode.db` |
-| Hermes | `~/.hermes/state.db` | `~/.hermes/state.db` | `%USERPROFILE%\.hermes\state.db` |
-| Qoder (sessions) | `~/.qoder/logs/sessions/` | `~/.qoder/logs/sessions/` plus WSL-mounted Windows user homes | `%USERPROFILE%\.qoder\logs\sessions\` |
-| Qoder (SQLite) | `~/Library/Application Support/Qoder/SharedClientCache/cache/db/local.db` | `~/.local/share/Qoder/SharedClientCache/cache/db/local.db` | `%LOCALAPPDATA%\Qoder\SharedClientCache\cache\db\local.db` |
-| Cursor | `~/Library/Application Support/Cursor/User/globalStorage/state.vscdb` | `~/.config/Cursor/User/globalStorage/state.vscdb` | `%APPDATA%\Cursor\User\globalStorage\state.vscdb` |
-
-Discovery behavior:
-
-- **Claude Code** — recursively scans `~/.claude/projects/**` for `.jsonl` files, including nested subagent logs.
-- **Codex** — recursively scans `~/.codex/sessions/**` for `.jsonl` files.
-- **OpenClaw** — scans each agent's `sessions/` directory under `~/.openclaw/agents/*/sessions/` and skips checkpoint files.
-- **OpenCode** — reads the SQLite database file directly instead of `.jsonl` logs.
-- **Hermes** — reads the SQLite database file (`state.db`) directly. Sessions without a recorded end time are still imported if they have token data (e.g. sessions from a force-quit).
-- **Qoder (sessions)** — recursively scans structured session segment logs (`logs/sessions/**/segments/*.jsonl`) and imports `model.response.completed` token events. On WSL, aiusage also checks mounted Windows user homes such as `/mnt/c/Users/<user>`, `/mnt/d/Users/<user>`, and `/mnt/e/Users/<user>` for the same Qoder session-log layout.
-- **Qoder (SQLite)** — reads the `local.db` SQLite database directly (`SharedClientCache/cache/db/local.db`) and imports assistant messages from the `chat_message` table, joined with `chat_record` for model information. This is the primary source on macOS and is tried alongside the sessions directory.
-- **Cursor** — reads Cursor's `state.vscdb` SQLite database directly and imports composer conversations with token usage data.
-
-> On Linux, OpenCode respects `$XDG_DATA_HOME` if set.
-
-Qoder Desktop also creates installation files under `Program Files`, UI/cache data under `AppData/Roaming/Qoder` and `AppData/Local/.qoder`, and transcripts under `%USERPROFILE%\.qoder\projects` or `%USERPROFILE%\.qoder\cache`. These are not imported as token records: desktop `Context usage update` log lines are repeated context-window snapshots, and transcripts/conversation-history files do not contain per-request token usage.
-
-### Custom Source Paths
-
-If you installed a tool to a non-default location, override the paths in the **Settings** page of the web dashboard (`http://localhost:3847/settings` → Sources section), or edit `~/.aiusage/config.json` directly:
-
-```json
-{
-  "sources": {
-    "claude-code": "/custom/path/.claude/projects",
-    "codex": "/custom/path/.codex/sessions",
-    "openclaw": "/custom/sessions-dir",
-    "opencode": "/custom/path/opencode.db",
-    "hermes": "/custom/path/.hermes/state.db",
-    "qoder": "/custom/path/.qoder/logs/sessions",
-    "qoder-db": "/custom/path/local.db",
-    "cursor": "/custom/path/state.vscdb"
-  }
-}
-```
-
-Only the paths you specify are overridden; unspecified tools fall back to their defaults. `qoder` points to the session logs directory; `qoder-db` points directly to the `local.db` SQLite file.
-
-## Database Visualization
-
-The local database is a standard SQLite file, so you can open it directly in DBeaver, TablePlus, DataGrip, DB Browser for SQLite, or any similar tool.
-
-```bash
-aiusage status
-# Shows the exact DB Path, schema version, and object counts
-```
-
-- Open `~/.aiusage/cache.db` as a SQLite database.
-- Prefer read-only mode in your database tool. `aiusage` writes to the same file and uses WAL mode.
-- If your tool asks about sidecar files, keep `cache.db-wal` and `cache.db-shm` alongside the main database file.
-- Start with the read-only views:
-  - `v_usage_records`: one row per usage record with normalized timestamp and token totals
-  - `v_tool_calls`: tool call rows joined with their parent usage record
-  - `v_sessions`: session-level aggregates for pivoting and charting
-- Raw internal tables remain available for advanced inspection:
-  - `records`
-  - `tool_calls`
-  - `synced_records`
-  - `sync_tombstones`
-
-## Tech Stack
-
-- **Runtime:** Node.js, TypeScript
-- **Database:** better-sqlite3 (local, WAL mode)
-- **CLI:** Commander.js
-- **Web:** SvelteKit + adapter-static
-- **Build:** tsup (core/cli), Vite (web)
-- **Sync:** GitHub API, AWS S3 / Cloudflare R2
-
-## Project Structure
-
-```text
-packages/
-  core/     - Shared types, database schema, pricing data
-  cli/      - CLI tool for parsing logs, querying data, cloud sync
-  web/      - SvelteKit web dashboard (SPA)
-```
-
-## FAQ
-
-### Does aiusage upload my data?
-
-No. aiusage is local-first. Your usage data stays on your machine unless you explicitly configure a sync backend.
-
-### Can I use aiusage across multiple machines?
-
-Yes. You can sync usage data through GitHub, S3, or R2 and then view the combined result from any configured machine or Docker deployment.
-
-### Does aiusage run a background parser automatically?
-
-No. By default, you run `aiusage parse` manually. You can automate parsing and syncing with cron, Task Scheduler, or your own scheduler.
-
-### Which assistants are supported?
-
-aiusage currently supports Claude Code, Codex, OpenClaw, OpenCode, Hermes, and Qoder.
-
-### Can I inspect the raw database myself?
+## Documentation
 
-Yes. aiusage stores data in a local SQLite database, and the README already documents how to open it in tools like DBeaver, TablePlus, DataGrip, or DB Browser for SQLite.
+Full documentation — CLI reference, Docker deployment, sync setup, desktop widget, and more — is available on the **[Docs page](https://aiusage.jtanx.com/docs)**.
 
 ## Friends
 
@@ -592,9 +56,9 @@ Yes. aiusage stores data in a local SQLite database, and the README already docu
 
 <a href="https://www.star-history.com/?repos=juliantanx%2Faiusage&type=date&logscale=&legend=top-left">
  <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&theme=dark&legend=top-left&t=20260528" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&legend=top-left&t=20260528" />
-   <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&legend=top-left&t=20260528" />
+   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&theme=dark&legend=top-left&t=20260603" />
+   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&legend=top-left&t=20260603" />
+   <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=juliantanx/aiusage&type=date&legend=top-left&t=20260603" />
  </picture>
 </a>