Workspace and collection
The workspace owns the memory. Collections organise documents and form part of a connection’s access grant.
Documentation
Connect Unforgetter to your agent.
A guided setup for the Cloud alpha: authorise a connection, choose the memory it may read, and verify the first useful retrieval.
Start with your client.
| Client | Current path |
|---|---|
| Codex | Cloud OAuth retrieval, scoped user-statement capture and automatic local context delivery run in the configured macOS Codex pilot. New-user setup and activation remain guided. |
| Claude web / Desktop | Remote MCP connection; the final client OAuth flow is still being verified. |
| Claude Code | Local proxy available in the original pilot. Confirm the Cloud path during setup. |
| Gemini Spark | Google documents custom MCP connections through Connected Apps. Available to eligible personal accounts, with region and language restrictions. The Unforgetter OAuth and retrieval flow has not yet been verified in Spark; confirm access during guided setup. |
| ChatGPT, Cursor, Grok Bot and other MCP clients | MCP support is a prerequisite, not evidence of an end-to-end Cloud test. Ask about your client when applying. |
Your first connection.
- 01
Receive an invitation
We confirm your client and sources, enable your account invitation, and provide the Cloud endpoint. Account creation and connecting an agent do not by themselves activate capture or maintenance.
- 02
Authorise the connection
Add the remote MCP server in your client and use its supported OAuth flow. Review the workspace and material the connection will be allowed to read.
- 03
Verify a source
Ask the agent to list the available documents and open a known project note. Check the source and current decision together.
- 04
Use the memory in a task
The agent can request context and search for sources. Where automatic memory is enabled during setup, verify a captured fact, a correction and retrieval in a fresh session before treating the full loop as active.
Use memory alongside your existing app connections.
If your AI already connects to Google Drive, you can use that connection to find and read files without Unforgetter. Unforgetter contributes saved decisions, project context and preferences. The agent can use that context when choosing what to search for and how to interpret a document, provided both connections are available in the same conversation.
| Part | What it contributes |
|---|---|
| Your existing Drive connection | Finds and reads documents with the access available to your account. |
| Unforgetter memory | Supplies saved project names, decisions, corrections and working preferences from authorised sources. |
| The agent | Combines relevant memory with current document contents to answer the task. |
For example, a saved decision might say that the team calls a spreadsheet ‘the influencer overview’ and uses its September tab for reporting. That can guide the agent toward the relevant file and tab. It still needs to open the document to check the current figures. This is an illustrative use case, not a measured improvement in search quality.
Keep a working Drive connection. During guided setup, first verify that the same agent can retrieve Unforgetter memory and use that connection. A ChatGPT Drive connection does not automatically connect Unforgetter, capture ChatGPT conversations or share your Google authorisation with Unforgetter.
The terms you will see.
Published generation
A set of source documents made available together. New publication can replace the serving generation.
Current and superseded
A decision can state what applies now or remain as historical context. Check this before acting on it.
Cloud and the original pilot.
Cloud has OAuth and four retrieval tools: list_documents, get_document, get_context and search_memory. With explicit memory:propose consent, a writable collection also accepts propose_memory.
In your signed-in Cloud account, Project permissions lets you allow or block proposed updates for one already approved agent/project pair, including a private pilot. The agent still needs OAuth proposal permission. This control keeps the existing approved data classes; processing and Mac capture are controlled separately.
Automatic capture, consolidation and context delivery run in a scoped internal Codex pilot. The Alpha16 Mac companion is available for guided setup with invited accounts. New users still need to connect a supported agent, approve their memory sources and activate processing. Installing the companion alone does not connect ordinary ChatGPT chats.
Private alpha
Pick up where you left off.
Free during the private alpha. We help you connect your first agent.