Capacity and usage limits
Read beta availability, session and weekly capacity, context limits, and external-provider quotas as separate constraints.
On this page
Current availability
Rogue is in free beta with usage limits. There is no checkout and no paid plan on sale; everyone is on the Free plan. Go and Max are announced on the pricing page and have not opened. Talk to the team if a project needs more capacity.
Capacity is not a deterministic number of prompts or completed apps. Workload, model activity, and tool execution vary by request. Use the account's observed usage and limit messages when planning a larger run, rather than estimating it in advance.
Inspect the account state
Preferences > Account shows the current session and weekly usage. Check both meters and the displayed reset time. A warning, a reached limit, and a provider failure are different conditions; use the error's context before retrying a request.
A usage session is independent of your authentication session. Signing out, opening a new tab, or restarting the browser does not reset the account's usage window.
Identify the limiting layer
| Constraint | Interpretation |
|---|---|
| Usage session | Five-hour window starting with a request when no usage session is open. |
| Weekly usage | Seven-day cadence from the first request; use the reset displayed in the account. |
| Sites context | Up to eight mentions, 16,000 characters of mention context, and 20,000 in the expanded request. |
| Text files | Up to four per selection, 48 KB per file, and 64 KB combined; context limits still apply. |
| External service | Provider quota, billing, timeout, and key limits are independent of Rogue capacity. |
Reduce avoidable work
Scope changes against the current artifact, supply the relevant source excerpt, and make validation explicit. Diagnose a preview load or publication error before repeating generation: retrying delivery and generating another artifact have different costs and effects.
When a limit is reached, follow its displayed reset or recovery instruction. Repeated submissions do not create extra capacity. External-service limits must be resolved in the service configuration or account responsible for those calls.