Memory Power

Message-time decisions, immediate recall, and incremental formation every 30 minutes

Memory Power stores long-term knowledge across Sessions. Sessions retain original conversations; Memory stores short records with source references.

Trigger flow

When automatic memory is enabled, the host calls Jev once after a user message enters the Session and before the Agent handles it:

  • save_scope: none, user, workspace, agent, or mixed.
  • should_recall: whether historical memory is needed immediately.

Recall adds relevant records to this turn's reference context. Saving records a source marker; a background worker extracts incremental Session knowledge every 30 minutes. Agent replies do not trigger another per-turn model call. mixed becomes separate records with distinct scopes.

Scopes

  • User: preferences of a trusted platform user, shared with that user's authorized Agents. The host must resolve identity; message text cannot establish it.
  • Workspace: project facts, decisions, and procedures, shared across Agents within the same project and isolated between projects.
  • Agent: private Agent experience.

Recalled content does not alter canonical messages or override instructions. Automatic processing excludes legacy global City memory. Core Memory is loaded from Agent PROFILE.md every turn, independently of Jev and keyword matching.

Agent Profile

remember.mode accepts profile | knowledge. Omitting it defaults to knowledge, storing searchable long-term information.

PROFILE.md lives alongside SOUL.md: SOUL defines the role; PROFILE holds explicit Agent-wide persistent agreements managed entirely by MemoryPower.

Use remember with target: "agent", mode: "profile", and the content to append immediately. New Sessions load the document too. Appends have no size cap. A daily check optimizes documents above 2,000 characters using exact edits, version checks, and an original backup. Valid agreements are not silently removed to meet the target.

Agent Profile applies to everyone using that Agent. Private User preferences must not fall back here when identity is unavailable. Existing wiki preferences are not automatically migrated.

Enabling

Automatic memory is disabled by default. Set enabled: true, decision_model_id, and formation_model_id in Memory configuration, then restart City. Jev is discovered when the decision model is omitted; the formation text model must be explicitly configured. The worker runs while City is running and recovers pending work after restart.

User scope also requires the host SDK's automatic.resolve_user callback. Without it, automatic User reads and writes are unavailable. Explicit remember, search, read, revise, and forget remain available.

Continue reading: