Memory Power

The Memory power manages durable facts, preferences, and experience across Sessions. Session remains the source of truth for complete conversations; MemoryPower does not own Session Messages.

Memory scopes

• Agent Memory — private experience and long-running state for one Agent, stored under agents/<agent_id>/memory.
• City Memory — shared across every Agent in the same City. Workspace facts land here, with the current workspace_id recorded as metadata.

Chat and Agent memory do not require a Workspace. Conversations without a project, including Feishu chats, can use long-term memory and save turn capture jobs. When a Workspace is bound, relevant records include its identifier. Project file and command operations still require a Workspace.

Workspace is not a memory scope of its own. Core Memory enters separate system blocks. Dynamic Recall for the current request is attached only to the current Turn's User Message model-input copy and never changes the original message.

City supplies a shared root to MemoryPower. Memory formation, persistence, recall, and isolation remain power responsibilities.

Continue with:

• Full Memory Power docs
• Messenger Power
• Task Power