If your approval flow requires the user to pause, switch devices, or survive a…

If your approval flow requires the user to pause, switch devices, or survive a server failover, the session model must be portable. When sessions live as provider-sealed blobs or server-bound IDs, the approval step becomes a sticky-session bug: the next device or service cannot reconstruct what the agent saw or why it asked for permission. Treat portable identity and durable workflow state as separate design concerns: export intelligible transcripts and workflow checkpoints you can resume elsewhere, and keep provider-specific sealed state optional, not required.