Connect ChatGPT.

Use the context you saved in a coding agent during a ChatGPT conversation, and keep useful new decisions in the same store.

Browser sign-in · Custom app

Start in MarkdownMem

Sign in to the memory desk, select or create a memory store, and open Connect an agent. Copy the exact endpoint. The examples use placeholder workspace and store names.

Set up your client

1. On ChatGPT web, open Settings → Security and login and enable Developer mode if it is available for your account. Workspace policy may restrict custom apps.
2. Open the Plugins page and use the + button to create a custom app named MarkdownMem. Paste your store's endpoint, choose OAuth, and use dynamic client registration (DCR) if asked to select the registration method. Do not choose No Authentication.
3. Connect the app, sign in to MarkdownMem in the browser, and approve the requested access. In a new conversation, select Developer mode from the + menu and enable MarkdownMem. Then run the read check below.

OpenAI changes custom-app navigation over time; follow its current guide if labels differ. Developer mode is available only on eligible plans and may require an administrator. Local desktop sessions using a Codex host can use the Codex setup instead.

Check that it reads the right memory

Create /context.md in the browser with a harmless project fact. In your agent, ask:

Use MarkdownMem to read /context.md. Tell me the project fact it contains. Don't change any notes.

To check portability, connect a second client to the same store and ask it to read that note. To check writes, ask one client to save a small test note and confirm it appears in the web editor. Keep the client's usual tool approval controls enabled.

Tell the agent when to use memory

Before working, search MarkdownMem for relevant context. Read the matching notes. After finishing, update durable decisions and preferences. Don't save credentials or whole conversation transcripts.

Add this to your client's project instructions if you want it to apply in future sessions. Connecting an MCP server does not automatically import built-in memory or make every conversation save notes.

If something does not connect

• Copy the endpoint again: a different store path selects different memory.
• Complete the client’s sign-in action and check your account still has access to the store.
• For browser OAuth, remove any old Authorization header or expired key that would take precedence.
• For cloud or remote sessions, configure the connection in that environment; local settings may not carry over.
• If only the interactive editor is missing, check MCP Apps support. Text tools can work even when a host does not render the UI.

Browser OAuth acts with your account's current permissions. For a narrower, unattended connection, see store-scoped automation keys.

Current client references

Instructions reviewed September 6, 2026 against the sources below. These are configuration guides, not a claim that every client version, plan, or managed workspace has been certified.

• OpenAI developer mode