memanto memory expire

Mark a memory expired. The content is kept and the memory still appears in recall, clearly labelled — this is the reversible alternative to memanto forget.

memanto memory expire MEMORY_ID [OPTIONS]

Arguments:

MEMORY_ID - ID of the memory to expire (required)

Options:

-r, --reason TEXT - Why it expired, stamped as expired_by (default: manual). Letters, digits, ., _ and - only.

Examples: Expire with the default reason:

memanto memory expire b7c3cf31-e537-49f1-abc4-c50ac6adeac5

Record why it was retired:

memanto memory expire b7c3cf31-e537-49f1-abc4-c50ac6adeac5 --reason superseded-by-rewrite

Output:

Memory expired.
  Memory ID: b7c3cf31-e537-49f1-abc4-c50ac6adeac5
  Reason: superseded-by-rewrite
  Still recallable and labelled [EXPIRED]. Restore with 'memanto memory restore b7c3cf31-...'.
  Completed in 2.03s

Afterwards, recall labels it and shows the stamp:

[EXPIRED] Deploys are manual via ssh
Expired Aug 18, 2026 03:56 PM · policy: superseded-by-rewrite

Notes:

Requires an active agent. Run memanto agent activate <agent-id> first.
Nothing is destroyed — content, tags, confidence and timestamps are untouched.
Reverse it with memanto memory restore.
Editing an expired memory does not revive it; only an explicit restore clears the stamp.
To retire memories in bulk by rule instead, use memanto policy apply.
Backed by the Expire Memory API endpoint.
See the Memory Lifecycle reference for the full model.

Getting Started

Agent Management

Session Management

Data

Migrate

Search & Discovery

Expiry Policy

AI Generation

System & Configuration

Schedule

Connect

memanto memory expire

memanto memory expire

​memanto memory expire

memanto memory expire