Why I Forked OpenUsage and Started Building a Linux-First Community Edition

For the last few months, AI coding tools have become a core part of my daily workflow.

Like many developers, I regularly switch between:

Claude Code
Codex
Cursor
Copilot
Gemini

The problem wasn't choosing a model.

The problem was tracking usage.

At some point I realized I was opening multiple dashboards every day just to answer one question:

How much AI usage do I have left?

The Problem

Every provider has its own limits.

Some reset every few hours.

Some reset daily.

Some have weekly quotas.

Some have token budgets.

After a while, keeping track of everything becomes annoying.

I wanted something simple:

Always visible
Lightweight
Lives in the system tray
Doesn't require opening a browser
Supports multiple providers

Discovering OpenUsage

While searching for a solution, I found OpenUsage.

The project was well designed and already supported many providers.

There was just one issue.

I use Linux.

As I started looking into Linux support, I discovered that the project was moving toward a Swift and macOS-first direction.

That made me think:

What if the cross-platform Tauri version continued as a community-driven project?

OpenUsage Community

That's how OpenUsage Community was born.

GitHub:

https://github.com/openusage-community/openusage

The goal is simple:

Build the best open-source AI usage tracker for Linux while maintaining cross-platform compatibility.

Current Features

Today the project supports:

Linux system tray integration
AppImage builds
Debian / Ubuntu packages
RPM packages
Multiple AI coding providers
Local-first architecture
Automatic updates

The application sits in the system tray and lets me check usage without opening multiple websites.

Why Linux Matters

One thing I noticed while working on the project:

Linux users are often left behind when desktop developer tools become successful.

Many projects eventually become:

macOS-first
proprietary
cloud-dependent

I wanted to take a different path.

OpenUsage Community focuses on:

Linux support
Open source development
Community contributions
Transparent roadmap
Cross-platform architecture

Building the Project

The technical stack is surprisingly enjoyable:

Tauri
Rust
TypeScript
Linux desktop integration
GitHub Actions
AppImage / DEB / RPM packaging

I'm currently working on:

GUI regression testing
Linux desktop testing
Better CI/CD pipelines
Packaging improvements
Community onboarding

Lessons Learned

The biggest lesson so far is that building software is the easy part.

Finding users is much harder.

The first few days after launching the project were a reminder that:

Most people won't care.
Some people will think it's unnecessary.
A few people will immediately understand the problem.

One of the first comments I received was:

This is exactly what I needed.

That single comment was more valuable than any star count.

It confirmed that the problem was real.

What's Next

My long-term vision is to make OpenUsage Community the best community-maintained AI usage tracker for developers.

Not just for Linux.

But eventually for:

Linux
macOS
Windows

while staying open source and community driven.

Looking For Feedback

If you're a Linux user and regularly use Claude Code, Codex, Cursor, Copilot or similar tools, I'd love to hear how you currently track usage limits.

Do you check dashboards manually?

Do you use scripts?

Or do you just wait until you hit the limit?

Project: