You correct it
“Use the original booking date. We rejected the rescheduled-date rule.”
Use cases
For the work that continues tomorrow.
Resume a project, carry a correction forward or switch agents with the current context available.
Pick the work.
Pick up where the project stopped.
The useful context is the decision that applies now and what still needs an answer.
You return to a booking feature after three weeks. The cancellation rule changed while you were away. The memory records the current rule, why it replaced the draft and the capacity question that remains open.
Add the late-cancellation fee to the booking flow.
Thought for 3 seconds
Read project memory
Called unforgetter · get_context({ collection_id: "booking-product", task_summary: "late cancellation fee" })
get_context({ collection_id: "booking-product", task_summary: "late cancellation fee" })
Retrieved 3 facts from booking-product
- Fee measures against the original booking date6 Aug · approved by you · supersedes the 22 July draft
- The capacity split is unresolvedDo not implement around it until it is decided
- Money is stored in minor units, never as a floatYour convention, carried into every agent that writes code
Kept as history: The rejected 22 July fee proposal
Added the late-cancellation fee. Cancellations inside 48 hours of the original booking date now charge late_fee_minor on the booking; rescheduling does not move that date. Changed booking/cancel.ts and booking/fees.ts, plus two cases in cancel.test.ts, all passing. capacity_split is untouched. Want me to open the PR?
Illustrative conversation
Keep the correction with the work.
The record changes
After publication, the new rule is current and the rejected option remains in history.
The next session can use it
The correction is available to retrieve, with its source, rather than depending on finding the old conversation.
Move to another tool with the same context.
Plan in Claude and continue in Codex. Both can retrieve the same published project memory, within the access you grant. You still review the answer; the benefit is having the existing decisions available before the agent starts.
Keep client material within its scope.
Give a connection access to the collection it needs for a client. The server applies that grant before browsing, reading or search. Named team roles and shared accounts are a separate feature still in build.
Share context between agents.
A published project record can help a second agent continue work. Unforgetter does not dispatch tasks between agents. Task handoff remains in your workflow; the memory gives the receiving agent a source to work from.
What you can try in the alpha.
Cloud provides retrieval and permissioned capture, with automatic maintenance in explicitly enabled collections. New-user enrollment and client setup remain guided; team features are in build. These examples illustrate the workflow, not measured outcomes.
Private alpha
Pick up where you left off.
Free during the private alpha. We help you connect your first agent.