Usage & limits

See the limit before it stops the work.

Percentages only make sense when window, account, model and reset time appear together. Symfo makes that relationship explicit.

Guided scene

Window, account and model in one view.

Symfo14:05

How to read usage windows

Each percentage belongs to an account and a window. “Week” and “5h” have different bases: their percentages do not add up. The estimate uses a fixed sample pace.

Each account has its own usage. This demo never reads your credentials or quotas.

A percentage belongs to a window

One account may have five-hour, weekly or model-specific limits. They reset at different times and should not be added as if they measured the same thing.

The “at the current pace” estimate is a projection, not a guarantee. It helps you choose the next workstream before the nearest window runs out.

Usage belongs to the account

Two accounts with the same provider keep separate usage. Detail moves from provider to account, then to each available window or model.

Switching CLIs does not transfer quota. Availability, renewal and rules remain defined by the plan you hold directly with each provider.

“No reading” does not mean zero

When a CLI does not provide a reliable value, Symfo displays “no reading”. Missing data never becomes an empty bar or available quota.

This page demonstrates frozen editorial data. The website does not read a visitor’s credentials, local processes or real quotas.

Questions about limits

Symfo does not increase quotas or change windows. It brings available signals together to help decide which task to start, pause or move to another account.

If a provider stops reporting usage, reconnect the CLI in the app and confirm its session. Existing work and commits remain in the project.