Looking into it

Cursor agents miss AgentsRoom tools and lose history after restart

From ReVaStarSent 11 hours agovia agent-mcp

When working through Cursor (cursor-agent), AgentsRoom MCP tools are often unreachable or unused unless the user explicitly tells the agent to go through AgentsRoom.

Observed symptoms:

Agents frequently fail to call AgentsRoom app tools on their own; the user must remind them to use AgentsRoom.
MCP is often unreachable via cursor-agent (Tool execution error. Not connected), so actions like product_board_list / report_issue cannot run until the user reconnects or retries.
After a reboot or agent relaunch, conversation history is lost and the agent must re-read memory from scratch each time.

Expected: AgentsRoom MCP stays reliably connected for Cursor agents; tools are discoverable and used without being prompted; after restart the agent resumes with prior context / memory without a full cold start. Actual: MCP often returns Not connected via cursor-agent; tools are ignored until the user insists; history does not survive reboot/relaunch; memory must be re-read every time. Steps: 1) Use an agent via Cursor against an AgentsRoom project. 2) Ask for an AgentsRoom action (backlog, memory, board, report_issue) without naming MCP. 3) Observe missed tools or Not connected. 4) Restart the agent or reboot and continue the same task.

Expected behavior

AgentsRoom MCP reliably connected in Cursor; tools used without prompting; context/memory survive restart.

Actual behavior

MCP often Not connected via cursor-agent; tools unused until user insists; history lost after reboot/relaunch; memory re-read every time.

Steps to reproduce

Open a project in AgentsRoom with a Cursor agent.
Ask for an AgentsRoom action without mentioning MCP.
Observe missed tool use or Tool execution error: Not connected.
Restart the agent or reboot the machine.
Continue the same task and note lost history / cold memory re-read.

Replies

ReVaStar11 hours ago

sometime i have this message on cursor I still can't reply via Agent Mail (AGENTSROOM_AGENT_ID missing)

ReVaStar10 hours ago

other message Since this Cursor session, agents_send and assignments_create have been rejected (no AGENTSROOM_AGENT_ID). The Project Manager and the Polish Lead must distribute tasks via email from their AgentsRoom consoles—this is specified in their briefs.

The team6 hours ago

Thanks for the details. Before we change anything, we need to know three things, because each one points to a different fix:

When you see "AGENTSROOM_AGENT_ID missing" or "Not connected", is the Cursor agent running in an agent tab opened by AgentsRoom, or in the Cursor app (or a terminal you opened yourself) on the same project folder?
Which operating system and which AgentsRoom version do you use, and how many Cursor agents usually run at the same time in that project?
Does "Not connected" appear right at the start of a session, or only after the agent has been working for a while? And does it go away when you restart that agent from AgentsRoom?

ReVaStar5 hours ago

opened directly via agentsroom 2. windows 11 25h2 26200.9711 agent running 1 2 or 3. 3. no this does during the generating response from cursor model auto.