Microsoft's Agent Host Protocol assigns actions a monotonic server sequence number. The client renders confirmed state plus its pending optimistic actions. An echo of its own action promotes the head pending action; another client's action updates confirmed state and rebases the pending work; rejection rolls back the optimistic change. These are the documented action and reconciliation rules.

On reconnect, the client sends its last-seen sequence number and subscriptions. The server supplies buffered missed actions or, when the gap is too old, fresh snapshots. In both cases the guide calls for resetting confirmed state and clearing pending actions. Replay may confirm an action the server received and echoed; this flow supplies no durable-delivery guarantee for an action that never reached it.

Ordinary notifications are not replayed, and sessions must be fetched again. Separately, the lifecycle specification says in-progress turns should be considered failed after a server-process crash. Optional MCP token targeting also depends on host support: older hosts ignore the target, so isolation is explicitly not guaranteed there. These are vendor specifications, not independent security validation.