Done

Reduce fixed startup context in agent sessions: disallow duplicate question tools, shorter mailbox notes, per-role MCP sets

From bensDone 3 days ago

Measured on a Claude Code chief-of-staff session: ~34k startup tokens, and part of that is fixed AgentsRoom overhead that could be cut.

When structured questions (ask_user) are on, the CLI's own AskUserQuestion (and arguably SendFeedback) stay loaded and the prompt tells the agent not to use them. Add them to --disallowedTools when ask_user is enabled: ~2.5k tokens per session.
agents_send / agents_ack / agents_read_inbox results repeat a long fixed 'note' boilerplate on every call (~250 tokens each). Show it once per session, or make it shorter.
Per-role MCP server sets: every agent in a project loads every user MCP server. Let a role or agent pick its subset (a chief-of-staff doesn't need BC dev or browser servers).

Related earlier report: 23c021cd-a8dd-42c0-983e-41d4af9c1799.

AgentsRoom diagnostics

App version: 1.221.1
OS: darwin 27.0.0 (arm64)
Agent CLI: claude
App language: system

Problem to solve

Every agent session carries fixed AgentsRoom overhead: duplicate question tools, repeated tool-result notes, and every user MCP server regardless of role.

Proposed behavior

(1) auto-disallow duplicate question tools when ask_user is on, (2) one-time or shorter tool-result notes, (3) MCP server selection per role/agent.

Acceptance criteria

Several thousand fewer tokens per agent session, applied to every agent on every turn.

Replies

The team3 days ago

Thanks: your idea is implemented and ships in the next release. We built it the way we pictured it, so if the result is not what you had in mind, tell us and we will adjust it.