{"version":"2.1.269","anchor":"team-mailboxmessaging-resolver-switched-from-state-snapshot","canonical_anchor":"sendmessage-cross-machine-permission-check-now-passes-a-deta","heading":"SendMessage and team mailbox internals switched to a detached 'ask' permission callback","tier":"internal","area":"Team Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/team-mailboxmessaging-resolver-switched-from-state-snapshot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### SendMessage and team mailbox internals switched to a detached 'ask' permission callback\n\nThe SendMessage tool's cross-machine and team-mailbox permission checks now go through a detached ask callback and accessor functions instead of passed-in state objects\n\n**Unclear.** Whether this changes any behavior visible to users of team messaging, or is purely an internal refactor, isn't clear from the evidence.\n\n**What**\n\n- In the SendMessage tool's bridge\/Remote Control send path, the permission-check helper used to be called directly with `context` and `canUseTool`. It's now invoked with an `ask` callback that calls the tool's `canUseTool` function with `{ detached: true }`. This affects the `isolatePeerMachines` approval flow (the \"isolatePeerMachines is enabled: sending to ... needs your approval\" prompt) and the message-post call, which now takes `{ tool, sessionId, message, assistantMessage }` instead of also passing `context` and `canUseTool` directly.\n\n- The team-messaging tool's internal resolver for mailbox, live-agent, stopped-agent, and cloud-session cases now reads application state and message history through accessor functions (`resolverState()`, `messages()`) instead of a captured state snapshot. Resuming or asking permission for a stopped or cloud agent is now routed through a wrapping effect call using the same detached `ask` pattern, rather than passing `canUseTool`\/`toolUseContext` directly.\n\n**Why**\n\nThis is an internal plumbing change to how permission checks are requested for cross-machine and team messaging, replacing direct state\/context passing with callbacks and accessors; it's not expected to change what approval prompts look like to a user.\n\n- Area: Team Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}