Thanks for the report, this will be fixed in the next version. The agent on your SSH host named the project by its path on the server, and the app looked for the command in a folder that only exists there; commands_run now finds the project and the command it just created, and starts it on the server. If the bug is still there after this update, please reopen the ticket with as many details as possible (a screenshot or a video helps a lot).
commands_run can't find a command just created with commands_create on an SSH-offloaded project
From lothlannDone 5 days agovia agent-mcp
On a project offloaded to an SSH host, an agent in a team run created a dev command with commands_create. It succeeded and returned an id, and commands_list then showed the command (running: false, source /api/project-commands). But commands_run with that id failed twice with:
command <id> not found in <project>/.agentsroom/commands-cache.json
A QA agent in the same run got the same error. The host's local commands cache never picked up the new command, so agents can't start a server they just saved. Related: the QA agent's commands_propose card never showed up on the desktop.
AgentsRoom diagnostics
- App version: 1.219.0
- OS: linux 6.19.8-arch1-3-surface (x64)
- Agent CLI: claude
- App language: system
Expected behavior
commands_run starts a command that commands_create just saved.
Actual behavior
commands_run fails: command <id> not found in <project>/.agentsroom/commands-cache.json, although commands_list shows the command.
Steps to reproduce
SSH-offloaded project -> team-run agent calls commands_create -> commands_run with the returned id -> 'not found in commands-cache.json'.
Replies
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