tokenade
GitHubenfr
Install

What Tokenade sends and stores

Updated

TL;DR — Tokenade 2.0 sends nothing: no telemetry, no usage counts, no account. Compaction and savings figures stay on your machine. It never contacts our servers: the daily update check goes to GitHub Releases (TOKENADE_NO_AUTO_UPDATE=1 turns it off), price lists come from LiteLLM and Helicone, and the embedding model from Hugging Face. The code is open source, so you can check this yourself.

Tokenade runs entirely on your machine. It has no telemetry: it sends no usage counts, no savings figures, no machine id, and nothing about your code, files, prompts or commands. There is no account and no licence to check. Tokenade is open source (MIT/Apache-2.0), so you can audit this claim in the code on GitHub.

Update checks

At most once every 24 hours, in the background, Tokenade checks GitHub Releases for a newer version and installs it if there is one. It downloads the latest release's signed manifest and, when there is an update, the binary for your platform. These requests carry nothing about you or your work beyond what any HTTPS request to GitHub carries.

To turn it off:

export TOKENADE_NO_AUTO_UPDATE=1

You can also run tokenade upgrade --off, which turns the background check off durably. See Upgrade and uninstall.

Price lists

To turn token counts into dollars (status line, tokenade gain, tokenade dashboard) and to know a model's context window (tokenade install's auto-compact threshold), Tokenade downloads two public price lists: LiteLLM's table from raw.githubusercontent.com and Helicone's cost list from helicone.ai. They are cached in ~/.tokenade/ and revalidated at most once a day. These are plain downloads: nothing about you or your usage is sent.

Requests you trigger

Other features need the network only when you or your agent use them, and none of them send anything to tokenade.net:

WhenDestinationWhat is sent
First semantic, --prompt or audit-claude-mdHugging Face (a pinned revision), or the model's GitHub Release if Hugging Face can't be reachedA one-time download of the embedding model (about 132 MB), checked against digests built into the binary.
tokenade web, tokenade read <url>The page you asked for. For some sites, their public API or a mirror instead: GitHub and GitLab APIs, Reddit, Hacker News (Algolia), Bluesky, X, Hugging Face, crates.io, and public Piped or Invidious instances for YouTube transcriptsYour URL, as your browser would send it.
tokenade searchDuckDuckGo, Bing, Brave, Yahoo, Ecosia, Mojeek and MarginaliaYour query. Disable search with TOKENADE_NO_WEBSEARCH=1.
tokenade judgeThe Anthropic API, with your own ANTHROPIC_API_KEYYour question with the raw and compacted output it checks.

When your agent's own web fetch or web search tool is redirected to tokenade web or tokenade search, the same rows apply.

The LLM proxy runs on 127.0.0.1 and forwards your agent's requests to the provider the agent already uses, and nowhere else. It is opt-in, except for the agents where tokenade install sets it up because hooks can't do the job.

What stays on your machine

  • Your savings figures. tokenade gain, tokenade dashboard and the status line read ~/.tokenade/ and render locally.
  • The stash (~/.cache/tokenade/stash/) holds the full outputs that were folded, so expand-ref can return them. Entries expire after 7 days.
  • The debug log (~/.tokenade/debug.log) records hook events, including command lines, with secrets redacted. It never leaves the machine. Install with --no-debug-log to keep it off.
  • Indexes and caches (index.db, semantic.db, dedup.db) describe your code for local search.

The full list is in Files and paths. tokenade uninstall deletes all of it.

Secrets

Before any output reaches your agent, Tokenade masks credentials it recognises (cloud keys, tokens, private keys, card numbers, high-entropy strings). E-mail addresses, phone numbers, IP and MAC addresses are only masked if you set TOKENADE_REDACT_PII=1. If a credential landed in a cache before you noticed, tokenade scrub-secret <substring> purges that exact string from every Tokenade file, and tokenade scrub-cache re-applies the redaction patterns to the stash and dedup.db.

Reporting a bug

Tokenade no longer uploads anything for bug reports. To report a problem, open an issue on GitHub and paste only what you choose to share, for example the output of tokenade healthcheck.

Coming from 1.x

Tokenade 1.x sent usage counts to tokenade.net to meter paid plans. 2.0 removes that reporter entirely, along with the sign-in and bug-report upload commands. The upgrade deletes the licence and account files 1.x left in ~/.tokenade/.