Thanks for the report, and sorry for the disruption. We found one likely cause of the slowness, and a fix will be available in the next version: since 1.219, when AgentsRoom is open on two computers signed in to the same account, they could keep telling each other about changes in an endless loop, every few seconds. That slows the app down even with a single agent, and it is worse on Windows. To confirm this and look into agents going inactive, could you tell us: 1) Is AgentsRoom also open on another computer with your account? (The Machines chip in the status bar lists them.) 2) Does the slowness stop when you close AgentsRoom on that other computer? 3) When the first agent goes inactive, does its console show "process exited", or does it just move to the Inactive list? 4) If you can, after reproducing it, send us the app log (Help menu). If the problem is still there after the update, please reopen this ticket with as many details as you can; a screenshot or a short video helps a lot.
Major issues with 1.220
From zthaggDone 3 days agovia public-page
I am unable to have more than one agent running at a time, as soon as I resume a second one, they first goes inactive. Even when I resume one agent the The program is running EXTREMELY slowly so I am unable to fully diagnose any further issues. This is causing a complete work stoppage for me.
Replies
Thanks for the report, and sorry for the disruption. We found one likely cause of the slowness, and a fix will be available in the next version: since 1.219, when AgentsRoom is open on two computers signed in to the same account, they could keep telling each other about changes in an endless loop, every few seconds. That slows the app down even with a single agent, and it is worse on Windows. To confirm this and look into agents going inactive, could you tell us: 1) Is AgentsRoom also open on another computer with your account? (The Machines chip in the status bar lists them.) 2) Does the slowness stop when you close AgentsRoom on that other computer? 3) When the first agent goes inactive, does its console show "process exited", or does it just move to the Inactive list? 4) If you can, after reproducing it, attach the files from the %APPDATA%\AgentsRoom\logs folder. If the problem is still there after the update, please reopen this ticket with as many details as you can; a screenshot or a short video helps a lot.
I learned that electron was having issues via my claude desktop app, it fixed running the electron mcp cmd via another route (node or npx I think).
Your request has been resolved and will be available in the next release.
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
- Chrome · Windows