OpenUsage Contributions

What I Built

OpenUsage is a cross-platform desktop application for tracking usage quotas and balances across AI coding tools. My contributions add local-first integrations for tools that store their token usage logs locally or on authenticated endpoints.

Why It Matters

Developer AI tooling is highly fragmented. Developers routinely use Cursor, Claude Code, and local utilities in the same workspace. Each provider has different reset windows, billing rules, and limits. OpenUsage aggregates these usage metrics so you know how much quota remains.

Engineering Approach

Instead of building a service that centralizes developer logs, my integrations read client state locally:

• Cursor Integration: Reads and parses Cursor’s local SQLite database files directly from the machine to construct billing periods, usage totals, and credit balances.
• Countergravity integration: Intercepts the local port, attaches local session authentication headers, and fetches usage stats from the status endpoints. This preserves privacy by keeping all telemetry and usage data on the developer’s local machine.