DSH Accounts & Usage

dsh-token-usage 4.0.1 keeps the package name and existing local ledger while adding one place to connect provider accounts and compare provider observations with DSH-observed usage. No telemetry, prompt storage, or DSH source patches.

Install

npx --yes github:shaomingbo/dsh-token-usage#v4.0.1

This installs into the web profile. Restart DSH yourself and hard-refresh the existing Web GUI; the installer never controls the DSH process.

npx --yes github:shaomingbo/dsh-token-usage#v4.0.1 status
npx --yes github:shaomingbo/dsh-token-usage#v4.0.1 uninstall
npx --yes github:shaomingbo/dsh-token-usage#v4.0.1 --profile web --source github:shaomingbo/dsh-token-usage#v4.0.1
npx --yes github:shaomingbo/dsh-token-usage#v4.0.1 --help

--profile defaults to web. --source defaults to the fixed v4.0.1 tag and may also be set with DSH_TOKEN_USAGE_SOURCE.

Local development

npx --yes github:shaomingbo/dsh-token-usage#v4.0.1 --source link:$PWD

The installer atomically changes only dependencies["dsh-token-usage"] and dsh.profile.bundles, runs pnpm install --ignore-scripts (with the documented corepack fallback), and restores the manifest if installation fails. Manual editing of those same two fields is a fallback, not the preferred installation path.

Product model

See CONTEXT.md for the canonical language: Connection, Credential, Product, Billing, Limit, Observation, Usage Ledger, and Attribution Rule.

• Provider connections: ChatGPT and Grok OAuth capabilities retain <DSH_HOME>/.oauth.json; Antigravity retains <DSH_HOME>/.antigravity-auth.json, multi-account activation, auto-failover, model route, and loopback proxy behavior. The UI starts OAuth/device authorization, supports Antigravity activation/removal, and imports GLM/Ollama API credentials through DSH Credentials. GLM, Ollama Local, and Ollama Cloud use the same internal provider-adapter seam.
• Official observations: provider-reported product, billing, allowance percentages, and resets are shown separately from local history. Limit values represent exact, range, dynamic, unpublished, or manual knowledge across rolling, fixed, billing-cycle, or rate windows.
• Local usage ledger: the existing usage.sqlite, request folding, project attribution, valuation, imports, corrections, exports, backups, retention, and /token-usage compatibility channel remain. It is a DSH-observed ledger, not a provider invoice.
• Compatibility: /account-usage is the unified loopback channel. /token-usage and /subscription-antigravity remain for the 4.x transition. When dsh-subscription-search is co-installed, it retains exclusive ownership of /subscription-search; this bundle registers only its callable ChatGPT/Grok backends through searchChain to avoid dual ownership.
• Optional search-chain capability: when the host exposes searchChain, ChatGPT/Grok may be registered as callable backends without returning credentials to callers. Search orchestration itself is not part of this package.

Ollama behavior

Ollama Local has no applicable remote quota. Ollama Cloud API keys provide documented Bearer-authenticated model access, but no dedicated official quota or validation endpoint is claimed; configured key status is labeled unverified. Settings-page allowance scraping is a separate explicit opt-in: the user manually pastes a Cookie header; only allowlisted Ollama session-cookie names are retained in the owner-only store. The plugin never reads Chrome or another browser profile, refuses redirects so credentials cannot cross origins, and labels parsed plan/session-hourly/weekly observations official_ui and brittle.

Privacy and requests

Secrets live only in owner-only files or DSH credentials. SQLite, plugin-owned RPC responses, logs, diagnostics, and exports contain no access token, refresh token, API key, Authorization header, Cookie header, or session-cookie value. RPC channels are loopback-only. Ordinary ledger operation makes no network requests; price updates and provider observation refreshes are explicit. Auth refresh and configured model routes contact only their provider endpoints as required. Redirects carrying credentials are rejected and provider origins are allowlisted.

Prompts, responses, request bodies, and tool arguments are never persisted by this plugin. Ordinary exports anonymize local identifiers by default. Complete backups remain private and uninstall keeps all data.

Data and migration

The existing path is unchanged:

<DSH_HOME>/profiles/<profile>/data/dsh-token-usage/

Linked development still falls back to <DSH_HOME>/dsh-token-usage/. Schema v6 is additive: legacy ledger, plans, and plan_rules tables remain; v5 plans and both quota windows are projected losslessly as manual estimates. Existing files are backed up before transactional migration. Newer schemas refuse normal writes and have a separate read-only diagnostic seam.

Development

pnpm install
npm run check
npm pack --dry-run

Tests use synthetic data and temporary DSH_HOME directories. The package targets the capabilities verified against DSH 0.1.1-rc.2 and Node 22.19+; it does not claim broader compatibility.

License

MIT