The problem
People start a task on a laptop, leave the desk, then need to continue on a phone. They may lose the page, repeat the search or reconstruct what they were doing.
Continuity is a designed capability, not something MCP or WebMCP guarantees by itself.
More than chat history
A safe transfer needs a task identifier, clear state, the information needed to resume, an expiry policy and a way to re-establish the user's identity. Sensitive information should not be copied into an insecure link.
Pause at the right point
If a task needs a signature, payment, submission or other consequential action, pause and ask the person to confirm on an appropriate device. A transfer must not silently transfer authority.
What should travel?
The goal, progress, non-sensitive context and next available step may travel with the task. Access credentials and unrestricted permissions should not be placed in a transfer payload.
What must be tested?
- Expired sessions and lost devices.
- Duplicate resume attempts.
- Changed permissions and interrupted networks.
- Partial completion and recovery on the receiving device.
The promise
The user should not have to start again. But continuity must be designed, secured and tested.