Skip to content

openusage-community/openusage

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

459 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

OpenUsage logo

OpenUsage Community

Made by developers for developers

Track all your AI coding subscriptions in one place.

OpenUsage Community is an independent, community-maintained continuation of the original OpenUsage project.

The goal of this fork is to continue the cross-platform Tauri-based direction with a strong focus on Linux support, while keeping macOS support and leaving room for future Windows support.

See your usage at a glance from your menu bar or system tray. No digging through dashboards.

OpenUsage Community Screenshot

Project Status

OpenUsage Community is currently focused on:

  • Linux support
  • Stable AppImage, .deb, and .rpm releases
  • System tray behavior across different Linux desktop environments
  • Keeping macOS support working
  • Preserving the lightweight Tauri-based architecture
  • Community-driven maintenance and provider contributions

This project is independent from the original OpenUsage project. It exists because the original project is moving toward a Swift/macOS-first direction, while this fork continues the cross-platform approach.

Download

Download the latest release

Available builds:

  • macOS Apple Silicon
  • macOS Intel
  • Linux AppImage
  • Linux .deb
  • Linux .rpm

The app auto-updates where supported. Install once and you're set.

Linux Notes

OpenUsage Community runs in the system tray.

On desktops without StatusNotifierItem/AppIndicator support, such as GNOME without the AppIndicator extension, a left-click on the tray icon may not open the panel. Use the tray menu's Show Stats entry or the global shortcut instead.

On Wayland, panel positioning is best-effort and depends on the compositor. The panel appears under the tray icon where the desktop environment allows it.

Reading credentials stored in the system keyring requires secret-tool, usually provided by the libsecret or libsecret-tools package.

Install on Linux

Grab the asset for your distro from the latest release.

Replace the version in the examples below if a newer release is available.

Fedora / RHEL

dnf pulls in the dependencies automatically:

sudo dnf install https://github.com/openusage-community/openusage/releases/download/v0.6.24/OpenUsage-0.6.24-1.x86_64.rpm

Debian / Ubuntu

curl -LO https://github.com/openusage-community/openusage/releases/download/v0.6.24/OpenUsage_0.6.24_amd64.deb
sudo apt install ./OpenUsage_0.6.24_amd64.deb

Any Linux distro

Use the AppImage for a portable build:

curl -L -o OpenUsage.AppImage https://github.com/openusage-community/openusage/releases/download/v0.6.24/OpenUsage_0.6.24_amd64.AppImage
chmod +x OpenUsage.AppImage
./OpenUsage.AppImage

After installing via .rpm or .deb, launch OpenUsage Community from your app menu. The app starts in the system tray.

If your desktop environment has no tray support, install an AppIndicator or StatusNotifier extension, or open the panel with the global shortcut.

Runtime dependencies are handled automatically by .rpm and .deb packages:

  • webkit2gtk-4.1
  • gtk3
  • AppIndicator library
  • secret-tool for providers that read from the system keyring

What It Does

OpenUsage Community lives in your menu bar or system tray and shows how much of your AI coding subscriptions you have used.

Progress bars, badges, clear labels. No mental math required.

  • One glance. All your AI tools in one panel.
  • Always up to date. Refreshes automatically on a schedule you pick.
  • Global shortcut. Toggle the panel from anywhere with a customizable keyboard shortcut.
  • Lightweight. Opens quickly and stays out of your way.
  • Plugin-based. New providers can be added without changing the whole app.
  • Local HTTP API. Other apps can read your usage data from 127.0.0.1:6736.
  • Proxy support. Route provider HTTP requests through a SOCKS5 or HTTP proxy.

Supported Providers

  • Amp / free tier, bonus, credits
  • Antigravity / all models
  • Claude / session, weekly, extra usage, local token usage with ccusage
  • Codex / session, weekly, reviews, credits
  • Copilot / premium, chat, completions
  • Cursor / credits, total usage, auto usage, API usage, on-demand, CLI auth
  • Factory / Droid / standard, premium tokens
  • Gemini / pro, flash, workspace/free/paid tier
  • Grok / credits used, plan, pay-as-you-go cap
  • JetBrains AI Assistant / quota, remaining
  • Kiro / credits, bonus credits, overages
  • Kimi Code / session, weekly
  • MiniMax / coding plan session
  • OpenCode Go / 5h, weekly, monthly spend limits
  • Windsurf / prompt credits, flex credits
  • Z.ai / session, weekly, web searches

Community contributions are welcome.

Want a provider that is not listed? Open an issue.

Open Source, Community Driven

OpenUsage Community is maintained as a community project.

The focus is simple:

  • reliable Linux support
  • practical cross-platform development
  • clean provider integrations
  • stable releases
  • small, reviewable changes

Contributions are welcome, especially:

  • Linux desktop fixes
  • packaging improvements
  • provider plugins
  • documentation
  • bug reports with clear reproduction steps
  • before/after screenshots for UI fixes

Plugins are currently bundled while the plugin API is being developed. The long-term goal is to make providers more flexible so users and contributors can build and load their own integrations.

How to Contribute

  • Add a provider. Each provider is implemented as a plugin. See the Plugin API.
  • Fix a bug. Pull requests are welcome. Provide reproduction steps and screenshots where relevant.
  • Improve Linux support. Test across GNOME, KDE Plasma, Xfce, Wayland, and X11.
  • Request a feature. Open an issue and explain the use case.

Keep changes focused. Avoid feature creep. Do not submit AI-generated code without reviewing, testing, and documenting it properly.

Relationship to OpenUsage

OpenUsage Community is based on the original OpenUsage project.

This fork is independent and community-maintained. It continues the Tauri-based cross-platform direction, with Linux as the primary focus.

The original project, its name, and its prior work are credited to the original author and contributors.

Credits

Based on the original OpenUsage project by Robin Ebers.

Inspired by CodexBar by @steipete.

Thanks to all original OpenUsage contributors and everyone helping improve cross-platform support.

License

MIT


Build from source

Warning: The main branch may contain unreleased changes. For regular use, prefer tagged releases. Tagged versions are expected to be tested before publishing.

Linux build prerequisites

Install the system libraries Tauri needs before building.

Debian / Ubuntu

sudo apt-get install -y libwebkit2gtk-4.1-dev libgtk-3-dev \
  libayatana-appindicator3-dev librsvg2-dev patchelf \
  libsecret-1-dev build-essential

Fedora

sudo dnf install -y webkit2gtk4.1-devel gtk3-devel \
  libappindicator-gtk3-devel librsvg2-devel \
  libsecret-devel patchelf

Stack

OpenUsage Community is built with:

  • Tauri
  • Rust
  • TypeScript
  • WebKitGTK on Linux

About

Community-driven continuation of OpenUsage. Building the best AI usage tracker for Linux, macOS and Windows.

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Packages

 
 
 

Contributors

Languages

  • JavaScript 48.4%
  • TypeScript 31.7%
  • Rust 19.5%
  • CSS 0.4%
  • Shell 0.0%
  • HTML 0.0%