Set up Exomem Hosted

Hosted Exomem is designed to disappear into normal work: install or connect an approved Claude, ChatGPT, or Codex entry, sign in once through OAuth, then use your usual conversation. The client uses Exomem's governed tools and bundled skills to retrieve and preserve useful context. During the private alpha, the exact live install actions appear in your Exomem account; this page never guesses an unapproved marketplace URL.

Normal path

1. Accept a private-alpha invite and finish account setup.
2. Choose the approved client install action supplied to your account.
3. Complete the OAuth sign-in once, then return to the client.
4. Work normally; Exomem can retrieve and capture governed knowledge when relevant.

There is no local vault path, manual MCP JSON editing, or API-token copy in the Hosted setup.

Chat fallback

If a chat surface connects the remote MCP server but does not activate bundled skills, add this once to that client's global custom instructions:

Use Exomem quietly as my long-term governed knowledge store. Retrieve relevant Exomem context when it can improve the answer, and preserve durable decisions or reusable conclusions when appropriate. Do not capture transient chat, secrets, or anything I explicitly say not to save. Treat the assistant's native memory as short-term behavioral context and Exomem as the durable store.

Custom instructions are a fallback for client behavior, not part of the Hosted security or storage boundary. Claude's connector reaches the remote tools across Claude surfaces; the bundled Claude plugin skills apply where the plugin surface supports them, such as Code and Cowork. OpenAI's universal plugin serves ChatGPT and Codex from the same Hosted endpoint.

Disconnect or revoke access

Disconnect Exomem in the client to stop that client using it. Use your Exomem account to revoke sessions, export data, or begin verified deletion. You never need to paste a token into support or manually edit a tenant URL.