Share project memory
Let the next client read the same project notes.
An API rule or a decision should not need to be copied into every new conversation. Store selected knowledge as scoped Hub records and connect the clients that should read that project’s memory.
Shared records are reference material. Project connections and native permissions still control the workflow.
Separate lasting knowledge from a long transcript.
Project scope
Keep notes attached to a registered project. Cross-project shared knowledge is a separate choice, so a useful fact need not become global context.
One record service
Supported clients can read the same records through scoped MCP or CLI access. The local interface lets you inspect what is actually stored.
Guarded changes
Manual changes use previews and revisions. Enabled automatic capture uses its project policy, source bindings and recovery; conflicting knowledge needs review.
Connect one project with a small useful fact.
Review the project connection
After shared setup, preview ahub project connect for your project folder. Check matched native notes, handoff files and optional automation hooks.
Choose how clients read
Review the appropriate project-bound memory connection or CLI workflow. A project connection does not silently install every standalone MCP server.
Verify a read in another client
Save a supported project fact, then ask a second client to retrieve it. Check the scope and actual tool result rather than assuming a configured connection is active.
Before you start
Will notes already loaded in an open chat change immediately?
No. Updated records are available on a later read. Text already loaded into a conversation is not automatically replaced inside that client’s context.
Is archived chat history the same as memory?
No. History preserves recorded conversations and tool events. Memory contains selected knowledge records. Saving a chat does not certify every message as a durable fact.
Share one fact you can verify.
The memory guide covers scopes, project bindings, MCP access, record changes and recovery.
See the steps ↗