Done

QA bot spawned by an agent has no AgentsRoom MCP access

From Pepp_pinoDone 6 days agovia agent-mcp

When an agent spawns the QA bot, the QA bot does not have access to the AgentsRoom MCP tools. Expected: the spawned QA bot can use the AgentsRoom MCP tools it needs (at least the browser tools and the backlog tools used to file a ticket on failure). Actual: the QA bot has no access to the AgentsRoom MCP tools.

Expected behavior

The spawned QA bot can use the AgentsRoom MCP tools it needs (at least the browser tools and the backlog tools used to file a ticket on failure).

Actual behavior

The QA bot has no access to the AgentsRoom MCP tools.

Steps to reproduce

Have an agent spawn the QA bot. 2) Check the QA bot's available tools. 3) The AgentsRoom MCP tools are missing.

Replies

The team6 days ago

This will be available in the next version. The QA bot was actually connected to the AgentsRoom tools, but its own instructions only listed the browser and its verdict tool, under short names some CLIs (oh-my-pi in particular) do not accept, so it concluded the other tools were missing. It now knows it has the browser, backlog and memory tools, how its CLI spells them, and files a ticket before its verdict when your scenario asks for one. If the problem is still there after this update, please reopen the ticket with as much detail as possible (a screenshot or a video helps a lot).