---
title: "Muse Code usage limits: the 5 hour window, in the sidebar"
url: https://helicon.sh/features/plan-limits
description: "Helicon shows the Muse Code 5 hour window and weekly cap exactly as the CLI reports them, in the sidebar and on the usage page, so a limit never arrives as a surprise."
updated: 2026-09-19
site: Helicon
---

# 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.

## 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.

> Helicon does not calculate or guess these. If Muse Code reports a figure, Helicon shows it. If it does not, Helicon shows nothing rather than inventing one.

## 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.

## Related

- [Cost at API rates](https://helicon.sh/features/cost-and-usage): See what every Muse Code thread would have cost at published per token rates, broken down by day, by model and by thread. A meter reading on your subscription, not a bill.
- [Session history and resume](https://helicon.sh/features/session-history): Every Muse Code session, grouped by project, with full history and one click resume. Sessions started in the muse terminal TUI are discovered and resumable too.
- [Inline diffs](https://helicon.sh/features/inline-diffs): Every file the agent edits lands as a diff at the point in the conversation where it happened, with the touched file open in a viewer beside the thread.
- [Approvals](https://helicon.sh/features/approvals): Every approval Muse Code raises appears in Helicon the moment it arrives. onRequest, promptUnmatched and denyUnmatched are mapped one to one, and allow all is an explicit opt in.
- [Projects and worktrees](https://helicon.sh/features/projects-and-worktrees): Helicon groups every Muse Code thread under the directory the agent worked in, isolated git worktrees included, so parallel work across repositories has one place to live.
- [Keyboard and palette](https://helicon.sh/features/command-palette): A command palette, slash commands and a model and reasoning effort picker. Every project, session and action in Helicon is reachable without the mouse.

---

Helicon is a free, MIT licensed, unofficial community client for Meta's Muse Code CLI. Not made, sponsored or endorsed by Meta. Source: https://helicon.sh/. Machine readable index: https://helicon.sh/llms.txt