A tension to resolve in the second version of sharing, once #531 to #533 are in place. Jackson, 2026-10-11: not now, but it should be addressed then.
The tension
In a shared conversation every prompt the agent raises in its thread can be answered by any member or guest collaborator (Shared conversations AC8). The reasoning was consistency: a collaborator who can tell the agent to spawn a Crew can approve it, and work a collaborator asked for should not be held up on an approval.
A Crew breaks that once it has launched. The Crews definition sends two things to the inbox instead of the thread:
- a Captain's request for a further seat;
- a seat's own request for approval of a command.
A server adds nothing to a guest's inbox, so both reach members only (Shared conversations AC12). A guest who asked for the Crew and approved its roster then watches it stall on a seat's approval that only a member can see, with nothing in the thread saying why.
The same shape shows up in the rule that an agent's inbox ask is refused in a shared conversation (AC13): the inbox is a private channel to one person, and a shared conversation is not.
Questions to answer
- Should a Crew's later requests appear in the Captain's thread when that thread is a shared conversation, so that whoever can answer its other prompts can answer these?
- If they stay in the inbox, what tells the people in the thread that the Crew is waiting, and on whom?
- A guest approves a roster as proposed and cannot change a seat's access (AC10). Does the same limit apply to a request for a further seat?
- Does any of this change for a server with several members and no guests, where every member has an inbox?
Related
Left for the same second version: a guest leaving one thread inside a project they hold as a whole, and what an ask to "every member" means when several members can write to the asking agent's thread.
A tension to resolve in the second version of sharing, once #531 to #533 are in place. Jackson, 2026-10-11: not now, but it should be addressed then.
The tension
In a shared conversation every prompt the agent raises in its thread can be answered by any member or guest collaborator (Shared conversations AC8). The reasoning was consistency: a collaborator who can tell the agent to spawn a Crew can approve it, and work a collaborator asked for should not be held up on an approval.
A Crew breaks that once it has launched. The Crews definition sends two things to the inbox instead of the thread:
A server adds nothing to a guest's inbox, so both reach members only (Shared conversations AC12). A guest who asked for the Crew and approved its roster then watches it stall on a seat's approval that only a member can see, with nothing in the thread saying why.
The same shape shows up in the rule that an agent's inbox ask is refused in a shared conversation (AC13): the inbox is a private channel to one person, and a shared conversation is not.
Questions to answer
Related
Left for the same second version: a guest leaving one thread inside a project they hold as a whole, and what an ask to "every member" means when several members can write to the asking agent's thread.