Skip to content

Features

Your real plan meter

Helicon reads the usage Muse Code itself reports and shows the 5 hour rolling window and the weekly cap in the sidebar and on the usage page. It is the same number the CLI has, surfaced where you can see it before a long run rather than after a refusal.

Last updated · Markdown version

Why it is in the sidebar

Hitting a cap halfway through a long refactor is the worst time to learn about it. Putting the meter next to the thread list means the information is present when you are deciding whether to start something big.

What is shown

  • The 5 hour rolling window, as Muse Code reports it.
  • The weekly cap, as Muse Code reports it.
  • Both again on the usage page, next to cost at API rates.

Frequently asked questions

Is this Helicon's estimate of my limit?

No. It is the value the Muse Code CLI reports over the protocol, displayed unchanged.

Does it work on every plan?

It shows whatever Muse Code reports for your plan. Where the CLI reports nothing, the meter is empty rather than guessed.

Where do I see it?

In the sidebar during normal work, and in detail on the usage page alongside cost at API rates.

Same Muse Code. Same subscription. Better interface. 

Free and MIT licensed. Signed Windows installer, universal macOS DMG, and a web build against a daemon you run.