Tray utility that monitors multiple AI assistant usage and estimates spend
Experience local monitoring of AI coding assistants with real-time session and weekly counters, a system tray dashboard, and a built-in CLI for scripting. AIUsage.NET, by LuigiElleBalotta, targets developers and power users who juggle multiple AI subscriptions and need a single view of token consumption and estimated spend. The tool reads credentials already stored on the machine, offers a read-only local HTTP API, and aggregates usage across several providers for quick oversight.
What the tool collects and presents
AIUsage.NET aggregates per-session, weekly, and per-model usage and shows remaining credits and local spend estimates. The app pulls usage data for providers such as Claude, Cursor, and GitHub Copilot, and offers a centralized dashboard plus a CLI that outputs the same metrics for scripts. The local HTTP API exposes read-only endpoints so other local applications can query usage without exporting private keys.
Does it affect system performance during monitoring?
Designed as a system tray utility, it stays unobtrusive while running. The app runs in the background and exposes a lightweight tray interface for quick checks rather than continuous heavy processing. It uses local reads of stored credentials and periodic polling of providers, which keeps active CPU and RAM demand low during idle monitoring. The design favours quick checks over sustained, resource-heavy operations.
Is it safe to use on a development machine?
Safety centers on local-only operations and read-only access. The tool reads credentials already present on the machine rather than asking for new API keys, and it exposes a read-only local HTTP API. Those two technical choices reduce the need to transfer secrets to remote services. The repository is open-source under the MIT License, which lets technically minded users inspect code and verify the data flows.
Do you need technical knowledge to operate it correctly?
It targets developers and power users rather than casual users. The presence of a CLI and an HTTP API indicates an expectation of scripting or tooling knowledge, while the system tray dashboard provides immediate visual cues. Setup requires placing the app alongside existing AI tools so it can read credentials; that workflow assumes familiarity with local developer environments and credential storage conventions.
Clear fit for developers who prefer local, inspectable monitoring with one caveat
AIUsage.NET serves developers and researchers who want local aggregation and spend estimates for multiple AI assistants; its open-source codebase and read-only API make auditing practical. The main caveat is that it requires a current desktop runtime to run, which adds a platform dependency for some environments. For anyone managing several AI subscriptions on Windows, it offers a practical, locally controlled monitoring option.
