Done

More agility in adaptive quota

From ASysuevDone 2 days ago

So, my idea is the following - I have two sets of accounts - one for work-related stuff, other for side projects. And I want to have adaptive quota separate on both sets. Like if my work Codex account is reaching it's limits, let's switch to Cursor. And if my personal Codex account is reaching it's limits - let's switch to Claude (and vice-versa).

Replies

The team2 days ago

Hi Artem, good news: you can already do this today, by combining two things.

  1. Tell AgentsRoom which accounts go together. Put your work projects in one sidebar folder and your side projects in another. Right-click each folder > Folder settings and pick the account for each provider (Work folder: work Claude, work Codex, Cursor. Personal folder: personal Claude, personal Codex). You can also do this per project in Project settings.

  2. Write one quota rule per account (Quota management > New rule, or Settings > AI providers & accounts > Quota rules):

  • Codex, Account = your work account, Any gauge ≥ 95% → "Change provider, model or effort" → Launch on Cursor
  • Codex, Account = your personal account, ≥ 95% → Launch on Claude
  • Claude, Account = your personal account, ≥ 95% → Launch on Codex

A rule set on a named account only reacts to launches on that account, so the work rule never touches your personal agents, and the other way round. When a rule sends a launch to another provider, that provider uses the account pinned on the folder (or project). So a personal agent moved to Claude runs on your personal Claude account.

Two things to know:

  • These rules apply when an agent starts. An agent that is already running keeps its tool, because switching tools would start a new conversation.
  • If both personal accounts are full at the same time, the launch goes to the first fallback and does not loop back.

If it doesn't work like this for you, reply here with a screenshot of your rules and we'll look into it.

Up to 3 images, or paste one straight from your clipboard. Big screenshots are shrunk in your browser before they are sent.