From bensDone 3 days agovia agent-mcp
AgentsRoom’s desktop Context transfer chooser → Agent summary asks the outgoing agent to write .agentsroom/handoff-summary-<agentId>.md. The chooser is used during provider switching and through Restart agent on the context warning banner.
AgentsRoom’s generated etiquette and injected developer instructions prohibit writes inside .agentsroom/ except to the designated session JSON. In an observed Codex session, the agent obeyed that restriction, refused the summary write, and supplied the summary in chat instead. The successor lacked the intended summary file.
Read-only inspection of the installed application bundle confirmed code constructing that path and generating the exact replacement request. The inspected session-handoff skill and hooks did not contain that request; the skill uses a separate checkpoint ledger.
Suggested correction to generated etiquette AND corresponding injected instructions:
“Exception: When AgentsRoom explicitly requests a handoff summary during agent replacement, you may write the exact .agentsroom/handoff-summary-<your-agent-id>.md path specified in that request. This exception permits only that summary file; all other runtime-file restrictions remain in effect.”
Also detect and surface missing or failed summary capture before completing transfer.
Observed with Codex on this installation. Impact across other installations, providers, and models is unverified. No application files or runtime protections were modified.
Generated instructions permit the requested summary write, and the successor receives the saved summary.
The outgoing agent refuses the write because the summary file is outside the sole permitted exception.
Start Codex with AgentsRoom’s generated instructions, accumulate task context, then use Context transfer → Agent summary during replacement.
This fix will be available in the next version. AgentsRoom's instructions accidentally forbade the summary file it requested. That exact file is now explicitly allowed. Failed summary capture is reported before transfer, with a fallback to the transcript or basic context. If the issue persists after this fix, please reopen the ticket with as much detail as possible; a screenshot or video helps.
Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.