Skip to main content

​
Tell users before they connect shared memory

If your app lets users share memory across multiple AI apps or agents, explain it before sending them to the MemoryOS consent page. Use plain language first. You can introduce Memory Passport as the place where users approve, review, and revoke access. Suggested product copy:
We use MemoryOS so you can choose which AI apps may remember and use your approved context. You can review or revoke access at any time at consent.memoryos.io/manage.

​
When to show this

Show this in at least one of these places:
  • onboarding
  • settings or integrations
  • the screen where the user clicks “Connect shared memory”
Example connect memory screen before redirecting to Memory Passport consent

​
Consent URL generation

Use the universal SDK helper to generate the consent link you send users to. 
from memoryos.universal import UniversalMemory

consent_url = UniversalMemory.consent_url(
    agent_id="your_global_agent_id",
    state="optional_user_session_state",
    categories=["preference", "goal"],
)
categories preselects the memory categories for this specific consent link. If you omit it, MemoryOS uses the global agent’s default categories. The user can still add or remove categories before approving. If your app needs to automatically mark “Memory connected” in its own UI, pass a redirect_uri that exists in your app: 
consent_url = UniversalMemory.consent_url(
    agent_id="your_global_agent_id",
    redirect_uri="https://yourapp.com/integrations/memoryos/callback",
    state="secure_random_state_token",
    categories=["preference", "fact"],
)
If you provide redirect_uri, your callback must:
  • verify the returned state server-side
  • mark the state token as consumed so it cannot be replayed
  • show a success page when status=granted
  • show a retry or cancellation page when status=denied
Callback templates are available in: 
examples/production-memoryos-callbacks/

​
Why this matters

Users should not need to discover MemoryOS on their own. Your app should:
  1. Explain that MemoryOS is being used
  2. Send the user into the consent flow
MemoryOS handles:
  • user authentication
  • consent
  • permission management