Your working style stays consistent
“Always write to clients formally and keep it short.”
The differenceThe next client draft can reflect your style without another briefing.
Hands
Sign in
Get started with Hands
An agreement from an earlier conversation. Last week's decision. The way you always like to work. Memory helps your Hand carry forward what still matters — so you don't have to explain how you work all over again.
A chat keeps what you said. But what happens to the decisions, agreements and preferences that still matter after the conversation ends? Memory keeps that context as separate knowledge — without digging through an entire old chat.
A new task should not require a new introduction. These are the kinds of agreements your Hand can build on.
“Always write to clients formally and keep it short.”
The differenceThe next client draft can reflect your style without another briefing.
“We are going with the green house style; the orange version is out.”
The differenceThe next step starts from the agreed direction, not a fresh debate.
“Forget the old price list; the new one applies from November.”
The differenceYou should be able to correct outdated agreements instead of explaining the change again.
Imagine not adding the same list of requirements to every new request. You describe what needs to happen now; your Hand can use the relevant agreements you made earlier.
Not an endless chat log, but knowledge objects you can search, explore and inspect. Your console also shows which information is proposed or needs another look.
Preferences, agreements, working methods and project knowledge are kept separately from the original chat.
See how knowledge, instructions and workflows relate to one another — in a list or a visual map.
Proposals, conflicts and superseded information are clearly marked. The Memory tab is currently for viewing, not direct editing.
It is not about saving the most conversations. It is about organising, connecting and inspecting what your Hand knows.
Your Hand works with individual knowledge objects for agreements, instructions, workflows and important context. These objects can be linked to one another. You can explore not only what was recorded, but how pieces of knowledge relate. Its usefulness still depends on what has actually been recorded and whether it is up to date.
No. Chat history shows what was said during conversations. Memory keeps reusable knowledge separately, with its own topic, type and status. An agreement no longer has to be buried in one old conversation.
No. Not every sentence automatically becomes a lasting memory. The Memory tab shows what has actually been recorded. If something matters for future work, make that explicit to your Hand and check how it appears.
Yes. You can search through knowledge objects in a list or explore them as a visual map. Connections may show how a workflow relates to a project or which instruction has replaced an older one. The animation at the top of this page is a concept visualisation, not a recording of the console.
Open a knowledge object to inspect its available details, including sources, relationships and change history when those have been recorded. Missing information is not presented as if it exists.
Memory distinguishes active information from proposals and superseded knowledge. Potential conflicts and items needing review can appear separately. The Memory tab is currently read-only, so you cannot edit entries directly there. Discuss corrections with your Hand, then check what was recorded.
No. Saved instructions and working methods are not permission to access new apps, files or accounts. Your Hand's separate access controls and approval rules still apply.
Memory belongs to your Hand, not a single chat or AI provider. When you use another connected AI with that same Hand, the knowledge base remains with the Hand. Which context is used during any given task depends on that task and the access you grant.
The console only provides access to the memory of Hands belonging to your account. It requests information from the correct Hand through controlled, signed requests, not a public memory listing.
The console may still show the last known counts, but your Hand needs to be active to retrieve current details. Simply opening the Memory tab or letting it refresh does not wake a sleeping Hand.
Memory works alongside your files, skills and connected apps to give your Hand a useful foundation for the next task.
Get started with your own Hand. Keep important agreements and context in view and move forward with less repetition.