Your coding pace. On your desktop.

Monitoring starts automatically when you launch Tokrate. From version 0.1.11, sharing starts only after you choose “Yes, let's contribute”. Choose “Only for local use” to keep local monitoring. Your saved OFF setting is preserved.

From version 0.1.11, the first-launch screen asks for optional community sharing. No sharing starts before an affirmative choice. Existing ON settings without a consent record require reconfirmation; saved OFF remains OFF. Withdraw at any time with the sharing toggle.

Only turns completed after launch or after you enable sharing are eligible; earlier history is never backfilled. Switching sharing off stops contribution and community requests, clears the queue, and hides community comparisons and alerts. Local monitoring continues. The public website is always free to view.

No prompts, code, paths or account details are uploaded. Reports use a persistent pseudonymous signing key; read what is collected and retained.

From version 0.1.10, Tokrate checks for software updates automatically. You choose when to install. Use Check for Updates in the app, or turn automatic checks off in its settings. This control is separate from community sharing.

Mac uses Sparkle with signed updates. Windows installers and Linux AppImages use a separate alpha update channel with verified package signatures. Linux .deb installations use the download page and your package manager. These signatures do not remove Windows first-install security warnings. If you have version 0.1.9 or earlier, install an updater-enabled release manually once.

Update checks contact tokrate.dev; downloads come from GitHub. They send no contribution identity or measurements. Read about update traffic and privacy.

These are early builds for testers, not finished stable releases. Both were built on their target operating system and passed parser, dashboard and native WebView checks with Codex, Claude Code and Grok fixtures. Installer upgrade/uninstall, real desktop integration, high-DPI behavior and WSL paths still need hands-on testing.

GitHub hosts these public downloads; no GitHub account is needed to download the release assets. Never attach prompts, code, credentials or raw agent transcripts to an issue.

Filter by coding tool, inference provider and model. Explore recent speed, previous-day comparisons and seven days of local history. Codex reports completed-turn throughput; Claude Code uses transcript-observed turn timing; Grok Build uses work turns including nested agents. These include tools and waiting. First-token timing is available only when Codex reports it; streaming speed and answer quality are not measured.

Missing or ambiguous Grok usage stays unavailable. Provider and model information remain Unknown when the logs do not establish them.

The companions are MIT licensed and contain no advertising or behavioral analytics SDKs. Check the code yourself—or ask your AI agent to review what leaves your computer.