Done

Trigger autoCloseIdleMinutes does not close idle trigger-spawned agents

From asantosDone 6 days agovia agent-mcp

Schedule and webhook triggers configured with autoCloseIdleMinutes (2, 3, 5 and 30 minutes) spawn throwaway agents that finish their run and go idle, but they are never closed. They accumulate in the project's agent list (about 12 per hour with four 15-minute triggers) and have to be closed by hand with agents_close. Observed over several hours on 2026-10-15/16: agents_list_live showed many trigger-spawned agents with status idle, isTemporary true, whose last activity was well past the configured idle window.

AgentsRoom diagnostics

  • App version: 1.192.0
  • OS: linux 7.2.9-1-cachyos (x64)
  • Agent CLI: claude
  • App language: system

Expected behavior

A trigger-spawned throwaway agent that stays idle longer than the trigger's autoCloseIdleMinutes is closed automatically and removed from the list.

Actual behavior

The agents stay idle in the list indefinitely; only a manual agents_close removes them.

Steps to reproduce

  1. Create a schedule trigger (every 15 min) with autoCloseIdleMinutes = 2 or 3. 2. Let it fire a few times; each run finishes and the agent goes idle. 3. Call agents_list_live after 30+ minutes: the idle trigger agents are still there.

Version or build

AgentsRoom desktop, October 2026

Replies

The team6 days ago

Hi Andre, thanks for the detailed report.

Your diagnostics show AgentsRoom 1.192.0, the same version as in your request of October 7, so your app has not updated since late September. In that version, "Close after inactivity" never closed a run whose console sat in a terminal tab, nor a run whose CLI drew a full-screen interface the app could not read. Both were fixed in 1.199.0: a run now closes once it has been inactive for the trigger's delay, unless you are looking at it.

An update is only installed when AgentsRoom is really quit (Quit, or "Update ready" in the footer), so an app left open for weeks keeps running its old version. Please quit and reopen it, or download the latest version from agentsroom.dev (on Arch-based systems you can also use the agentsroom-bin package from the AUR).

We also fixed what made a working auto-close look broken: a closed run stayed in agents_list_live as an "offline" member until the trigger's history dropped it. From the next version, a closed run leaves that list, and /v1/agents of the local status API, just like it already leaves the sidebar. A run still listed as "idle" or "busy" really has an open console.

If your trigger runs still stay open after updating, please reopen this ticket with as many details as possible (a screenshot or a short video helps a lot).

The team6 days ago

Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.

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