Can I use two accounts to get more usage?

Why profiles don’t raise usage limits

Because the limit belongs to the account, not to the profile — and stacking accounts to get around it is a thing Muster will not help you do.

What a profile actually is

A CLI profile is an independent installation of the CLI: its own login, transcripts, history and MCP configuration. Two profiles signed into the same account share that account’s usage window, because the window is the provider’s, measured per account.

Two profiles on two different accounts have two windows — and that is exactly the arrangement most providers’ terms forbid when it is one person doing it to get more capacity.

Why Muster shows the limit but never works around it

The overview tab shows, per profile, the last limit the CLI reported for it. Showing it is useful: it tells you which identity is close to the edge before a front dies mid-task.

Rotating to another account when one hits its limit would be a two-line feature. It is not there, and will not be, because the product’s argument is that it does not lie to you about what agents did — and a tool that quietly circumvents the terms you accepted is a tool that lies to somebody.

What to do instead

When you are near the window, the levers are real ones:

• compact the expensive session — Muster will tell you when compacting pays for itself;
• run fewer fronts;
• move the mechanical tasks to a cheaper model, pinned on the role;
• or simply wait for the window to roll.

See The 5-hour window.