Context Portability

Context portability is an AI UX pattern that makes prompts, files, memories, and tool state move cleanly across apps or sessions as legible payloads. Users are not trapped re-explaining context when they switch surfaces.

Share

Interactive demo

Chat · Acme renewal

Acme renewal

Agent drafted a CRM note from your conversation.

After the agent suggests continuing in CRM

Agent

I can log this renewal brief in CRM. Want me to open the handoff?

Overview

The design problem

How might we design context portability so people can trust and act on AI output?

Use this pattern

When this pattern fits

  • Essential for cross-app agents, tool-calling assistants, and multi-step workflows where users benefit from inspecting and editing the context payload that travels across each boundary.

Avoid this pattern

When to skip or lighten it

  • Single-app tools with no ecosystem to port into.
  • Highly sensitive contexts that must not leave a compliance boundary.
  • Throwaway chats where portability adds ceremony without reuse.

States

State model coming soon

Key UX elements

Key UX elements coming soon

Anti-patterns to avoid

  • Opaque blobs users cannot inspect before export.

  • Portable packages that silently include secrets.

  • One-way lock-in with import but no export.

  • Losing citations and permissions metadata in transit.

How products use it

ProductImplementation
Model Context ProtocolStandardized context and tool interfaces across clients.
ChatGPTConnectors and shared context across GPT surfaces.
ZapierMapped fields that carry data between automations.
Apple ShortcutsVariables passed across multi-app shortcut steps.

Implementation

Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.

Generate a production-ready implementation of the "Context Portability" AI interface design pattern.

Pattern Definition:

Frequently asked questions

What is context portability in AI UX?

It is the ability to move conversation context, files, and tool state between apps or sessions in a form users can inspect and control.

What should a portable package include?

Messages or summaries, attachments by reference, tool allowlists, and provenance. Exclude secrets unless explicitly opted in.

How does this relate to shared session links?

Shared links hand off a live or snapshot session inside one product. Portability aims at cross-app, often file- or protocol-based handoff.

Why does legibility matter?

If users cannot read what is being transferred, they cannot consent. Portable does not mean invisible.

Weekly AI UX in your inbox

Weekly AI interface UX notes and resources on Substack, no spam, unsubscribe anytime.

Subscribe on Substack