Decisions and corrections
What you settled, why, and which earlier decision it replaces.
Your next conversation starts with context.
Your next conversation starts with context.
Connect an agent, choose what it should know, and bring the current memory into the work you already do.
Your first project, in three steps.
- 01
Connect with us
We help you authorise a supported client and confirm which workspace it can read.
- 02
Choose a starting memory
Bring useful project notes, decisions or preferences. We agree the source and update process during setup; a prepared vault is not required to apply.
- 03
Continue your work
The agent retrieves the published context and can open its sources. You review its work with the current decisions available.
What becomes memory?
Your inbox and calendar stay in the apps that already hold them. Your agents can use their existing connections.
Current state and open questions
Where a project stands and what still needs an answer.
Preferences and methods
How you write, review and work, available across connected tools.
When a decision changes, keep the history.
An illustrative example of maintained memory. The updated record is what the next conversation should work from.
Monday · Claude
You change the date and ask for a decision note.
Move the launch from 29 October to 12 November. Keep the beta invite-only. Write a short decision note for the project.
Thought for 2 seconds
Read project memory
Called unforgetter · get_context({ collection_id: "launch", task_summary: "check the previous launch plan" })
get_context({ collection_id: "launch", task_summary: "check the previous launch plan" })
Retrieved 2 facts from launch
- Launch date: 29 OctoberThe plan before your message above
- Beta is invite-onlyUnchanged by this decision
Launch decision: 12 November replaces 29 October. The beta remains invite-only. Use 12 November in future launch updates; keep the October date as history.
ClaudeUnforgetterCodex
Same project. Next conversation.
Unforgetter keeps Monday’s new launch date. Below, Codex retrieves that decision in a fresh conversation on Thursday.
Draft a short launch update for the team.
Thought for 3 seconds
Read project memory
Called unforgetter · get_context({ collection_id: "launch", task_summary: "draft the team launch update" })
get_context({ collection_id: "launch", task_summary: "draft the team launch update" })
Retrieved 2 facts from launch
- Launch date: 12 NovemberYour Monday message in Claude · published decision · replaces 29 October
- Beta stays invite-onlyYour Monday message in Claude
Kept as history: 29 October is the previous date, retained as history
Team update: we're launching on 12 November. Until then, the beta stays invite-only. Please use the new date in launch plans and communications; it replaces 29 October.
Illustrative conversation
What happens automatically today?
The Cloud runtime accepts permitted memory proposals and maintains explicitly enabled collections. In the configured Codex pilot, local hooks capture user statements and return current context without a separate memory prompt.
Captured statements are processed before they become active memory. Corrections can replace an old value while preserving unrelated source details. This is a scoped internal pilot, not automatic enrollment for every account or verified capture of every assistant and tool result. We agree and verify the setup for each invited user.
Bring the relevant context, then open the source.
The agent asks for a briefing, browses available documents or searches within its permitted memory. Source references and freshness help it check what applies. An agent still needs to use that context correctly; memory does not guarantee a mistake-free answer.
Skills
Keep your reusable instructions with the work.
A skill describes how to do a task: your code-review process, writing method or research checklist. Project memory supplies what the task is about.
The planned skill library keeps approved instructions and references with their names, versions and sources. The agent should find the relevant skill and apply it without you managing a separate copy for every tool.
Automatic discovery, delivery and activation are still in build. The first integrations target Codex and Claude Code with instruction-only skills. New third-party skills and additional permissions require approval; a downloaded file alone does not prove that an agent is using it.
Cloud alpha · checked 14 September 2026
Available in the private alpha.
| Area | Current scope |
|---|---|
| Cloud retrieval | Running with authorised collections, document browsing, source reading and search. |
| Authentication | OAuth exists in the Cloud runtime. Client verification and invitations remain guided. |
| Capture and maintenance | Running in an explicitly enabled internal Cloud pilot. New-user enrollment, first activation and client setup remain guided. |
| Ownership | Source memory is readable Markdown. Packaged export and self-service deletion are in build. |
| Teams | Single-owner alpha workspaces. Team roles and invitations are in build. |
Private alpha
Pick up where you left off.
Free during the private alpha. We help you connect your first agent.