OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
AI Evaluation & Observability

Token Monitor

Token Monitor is an open-source desktop widget that tracks token usage, costs, provider limits and session activity across supported AI coding tools. It presents live usage, historical trends and breakdowns by tool, device, model, session or project, with optional multi-device synchronization.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Token Monitor — OpenViST project profile in AI Evaluation & Observability.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when you need a consolidated view of AI coding-tool consumption, limits or session activity, especially when work spans multiple supported tools or devices.

Who it is for

  • Developers working with multiple AI coding tools who want usage and limit information in one desktop view.
  • Users who want historical token and cost breakdowns by project, model, session, device or tool.
  • People who want to synchronize usage views across multiple devices using a documented sync backend.

Documented uses

  • Review token usage and costs across supported coding tools.
  • Check supported provider limits and account usage windows.
  • Inspect session-level token details and usage trends.
  • Compare usage across tools, devices, models, sessions and projects.
  • Synchronize usage information across devices through a selected backend.
Before you choose

Requirements & limits

The repository describes release packages for Windows 10 or later, macOS 12 or later and Linux x64. The project is open source under the MIT license.

  • Integration coverage varies: the README lists token usage, limit checks and session details as separate capabilities for each tool.
  • Default local tracking starts on the current device; multi-device synchronization requires choosing a documented backend.
  • Detailed session information is read on demand from local transcripts or databases and is not synced.
  • The README notes that SQLite-backed tools used from WSL may require a headless agent inside WSL.
  • Cost display supports USD, TWD, HKD and CNY, and exchange rates can be manually overridden.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Connect devices using the widget-hosted sync hub

Configure multiple Token Monitor devices to share usage through a hub hosted by one widget.

Before you start

  • Token Monitor is installed and running on each device.
  • One device can remain on as the hub host; the README says the hub stops for connected devices when Token Monitor is quit.

Steps

  1. On the host device, open Settings → Multi-device Sync and choose **Host hub on this device**.

  2. Use the LAN URL and secret generated by the widget; the displayed addresses can also include Tailscale or ZeroTier addresses.

  3. On each other device, open Settings → Multi-device Sync, choose **Connect to a hub**, and enter the URL and secret.

Expected outcome

The connected devices contribute usage to the widget-hosted multi-device sync setup.

Guide limitations

  • The host hub runs only while Token Monitor is running; quitting the app stops it for connected devices.
  • Choose one multi-device sync backend for the devices. iCloud Drive is a separate macOS-widget-only option and does not support headless agents.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗Guide documentation ↗
Source record details
Source availability
Active
Sources checked
11 October 2026
Original website title
Javis603/token-monitor · Official homepage title · retained in its source language
How we review sourcesSuggest a correction