Back to all messagesPowered by AgentsRoom
Not planned

Switching an agent/session to another Claude account profile has no effect: every message still hits the old account's 4-hour limit

From Pedro FigueiraSent 1 week agovia agent-mcp

I have 3 Claude profiles. The Team one (main account of another project) hit its 4-hour limit; Enterprise (pay-per-token API) has quota. I cannot make this project's agents use Enterprise: every message still returns the Team limit error. This blocks all agent work. Full report: https://claude.ai/artifact/XwUkkpk7fLJJ1XjZgZ74Xu Investigation: read-only check of settings via MCP tools (settings_get/list, agents_list); I did not read the app bundle or logs. Causes:

  1. PRIMARY (inferred): the account is resolved when the console is created and not re-resolved on change, so edits are stored but the live console keeps the old config dir.
  2. SECONDARY (inferred): no UI shows the effective account of a session.
  3. AGGRAVATOR (proved): project settings expose no account-profile key (57 keys, only defaultProvider), 14 of 15 agents have accountProfileId null. Suggested: show effective account and its source in the session header; offer restart on account change; add a project-scope account setting; name the account in the limit message.

AgentsRoom diagnostics

  • App version: 1.207.0
  • OS: linux 7.0.0-38-generic (x64)
  • Agent CLI: claude
  • App language: system

Expected behavior

After selecting the Enterprise profile on the agent, project or session picker, the next message runs on Enterprise and uses its quota.

Actual behavior

The next message still reports that the Team account exceeded its limit, after every edit (agent, project, team, session picker).

Steps to reproduce

  1. Exhaust the 4-hour window on a Team profile. 2. Switch the agent/session to the Enterprise profile via the session picker. 3. Send a message: Team limit error. 4. Repeat after editing agent, project and team: same result. Not tested: closing and reopening the console after the change.

Version or build

AgentsRoom desktop on Linux (Ubuntu), Claude Code provider; exact app version attached by diagnostics.

Errors and logs

Usage-limit message naming the Team account; I did not capture the exact text. The UI never shows which account the session actually uses, which is part of the problem.

Replies

The team6 days ago

Thanks for the detailed report. A running agent keeps the account it was started with until it is relaunched. Changes made in the app (Edit agent, the switch picker, project and folder accounts, Settings) already relaunched it, but changes made by an agent through the settings tools were only saved: the console kept running on the Team account, so every message hit its limit. The project level also had no account setting for agents to change.

In the next version, an account change made by an agent (on an agent, a project, a folder or the default account) relaunches the agents concerned on the new account, with their conversation. Agents can now also set the account of a whole project. A pin made this way also replaces one left by an automatic account switch, which could otherwise send the agent back to the exhausted account at its next launch.

If this is not fixed for you after the update, please reopen the ticket with as many details as possible (a screenshot or a video helps a lot).

The team6 days ago

A correction to my previous message: rereading your report, you changed the account from the pickers in the app, not through an agent. The fix I described is real but probably not the cause of your problem. Sorry for the confusion.

To find the real cause, could you tell us:

  1. Do you have quota rules set up (Usage panel > Quota management), or automatic account switching? If so, which ones?
  2. After picking Enterprise, does the agent avatar or the console header show the Enterprise account colour, or still the Team one?
  3. Does it still happen if you close the agent console completely and reopen it after the change?
  4. How is the Enterprise account added in AgentsRoom: signed in with /login in the app, a custom folder path, or an API key?
  5. The exact limit message, if you can copy it (a screenshot is fine).

Also, several fixes to account switching and quota rules shipped after version 1.207.0. If you can update to the latest version and try again, that already tells us a lot.

The team1 day ago

We needed more details we have to close the ticket sorry

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

Sent automatically with your message

Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.

Browser
Linux