Update Memory

When To Update

• A user explicitly corrects old information.
• A preference, plan, identity detail, or constraint changes.
• An old Summary has expired but might still be recalled.
• An operator discovers an incorrect memory and needs a governance action.

Recommended Pattern: Write a Correction Message

When a user corrects information, write that correction as new Message input.

JavaScript

await session.addMessages([
  {
    role: "user",
    content: "Correction: next Wednesday I am going to Shenzhen, not Shanghai.",
    metadata: {
      source: "correction"
    },
    timestamp: "2026-04-24T11:00:00Z"
  }
]);

cURL

curl -X POST "http://localhost:8000/api/sessions/session_xxx/messages" \
  -H "Authorization: Api-Key your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      {
        "role": "user",
        "content": "Correction: next Wednesday I am going to Shenzhen, not Shanghai.",
        "metadata": {
          "source": "correction"
        },
        "timestamp": "2026-04-24T11:00:00Z"
      }
    ]
  }'

GUMem treats this Message as new evidence. Later Summary generation should keep the latest or more certain information and avoid using the old item as current truth.

Why Not Patch Summary Directly

Summary is long-term memory supported by Facts. Overwriting Summary directly loses important properties:

• The system cannot explain which Message caused the change.
• The system cannot distinguish user correction, system correction, and operator governance.
• The relationship between old Facts and new Facts is lost.
• Audit and deletion become harder.

Use new Message input for user corrections. Use governance flows for operator repair or compliance actions.

Governance States

Summary can move through management states:

State	Description
active	Default state, eligible for recall.
deprioritized	Kept but less likely to be recalled.
archived	Retained for archive or audit, normally not recalled.
deleted	Deleted or soft-deleted, should not be recalled.

These are governance capabilities. This page does not assume a stable public PATCH /memory endpoint. Use the admin or management API exposed by your deployment.

Checkpoint

After writing a correction Message, query Memory again with the same query. Expected behavior:

• The returned Summary reflects the corrected information.
• Details can trace the result to the new Message or Facts.
• The Agent no longer treats the old Summary as current truth.

Next Step

Read Delete Memory to handle memory removal requests.