# Usagestat v2.0.2

This stable update improves provider compatibility and local accounting, and
adds three opt-in web providers. Stable archives and npm packages continue to
target Linux x64/ARM64 with glibc 2.39+. Windows/macOS remain on the existing
separate alpha channel; native candidate checks do not expand stable support.

## Provider and accounting updates

- Antigravity and Antigravity CLI send the current platform-specific Hub
  User-Agent. Permission and subscription denials remain distinct from expired
  authentication; the change does not certify access for every account.
- Codex local history reads `token_usage_record` request ledgers, validates
  thread/execution-session ownership and explicit child-history boundaries,
  and reconciles legacy mirrors, replays and archived copies. Private cache
  version 7 reparses older summaries. Model prices remain per request; missing
  model/pricing evidence stays unknown.
- OpenCode Go supports current credentials and assistant/completed-compaction
  history in explicitly selected OpenCode 2 databases. Migrated messages count
  once. An empty current credential table means logout; an unreadable database
  is an error. Neither revives an old imported `auth.json` login. Explicit
  manual credentials and selected database paths retain their precedence.
- Cursor Teams prefer two usable model pools over the legacy dollar meter.
  Combined usage appears only when the provider reports it. Zero placeholders
  beside positive dollar spend retain the older dollar path.
- Muse Code can recover a blank browser email through the selected team's
  matching membership and CLI account. It retains explicit team/plan checks.

## New opt-in providers and dashboard setup

The bundle now includes 100 providers. The new `museai` (muse.ai, separate from
Muse Code), `lithosai` and `workbuddy` entries are disabled by default and use
their own provider icons. Configure only the providers you use under dashboard
**Settings → Collection**; Display preferences remain independent.

- **muse.ai:** supply its website session Cookie header. Bounded discovery
  finds the deploy's subscription action and retains only its public action ID.
  Weekly subscription usage and additional/top-up amounts remain distinct.
- **LithosAI:** supply both `__Host-console_session` and `__Host-console_csrf`
  from the same console session. The native host echoes CSRF only on permitted
  HTTPS console routes. Signed prepaid balances are separate from optional
  measured UTC spend; a failed spend read does not erase a valid balance.
- **WorkBuddy:** supply its website Cookie header and the full **Browser
  User-Agent** from the same browser, shown under provider-specific settings.
  Monthly credits remain available if optional package/reset reads fail.

Automatic browser import and WorkBuddy desktop credential decryption are not
implemented for these providers. Native and synthetic fixtures qualify their
parsers, accounting and scope controls; live authenticated sessions remain
unqualified. TypeSafe's Cloudflare protection remains an explicit limitation:
this release does not claim a challenge bypass or convert failure into zero
usage or expired authentication.

## Upgrade and compatibility

Install the CLI, daemon and plugins together, then refresh the dashboard.

```sh
npm install --global @hashimkarim/usagestat@2.0.2 --include=optional --ignore-scripts
```

Stable RPMs retain the feed, optional daily update timer and transaction hook
introduced in 2.0.1. A package upgrade refreshes already-running RPM-owned
services while preserving configuration, history, stopped services and SDK-owned
installations. Daily downloads still require enabling the packaged timer:

```sh
sudo dnf upgrade usagestat
sudo systemctl enable --now usagestat-rpm-update.timer
```

`/v1/providers`, `/v1/usage` and optional `agenticdriver.usage.v2` ingestion keep
their stable contracts, exact account/subject bindings, separate credentials,
deduplication and cost semantics. AgenticDriver RC.2 remains compatible; no new
HTTP major version or application authentication migration is required. The
dashboard collection catalogue adds optional setup hints which older clients
can ignore. Shared provider-icons stays pinned to `0.1.0-alpha.1`.

Existing releases and package versions are immutable. Check the
[publication record](https://github.com/hashimkarim/usagestat/blob/main/docs/releases/v2.0.2-publication.md)
for actual per-channel availability and the
[installation guide](https://github.com/hashimkarim/usagestat/blob/main/docs/installation.md)
for upgrade commands. A published release or queued feed build does not silently
upgrade an existing installation or change its credentials.