plmhub
All commands

Memory

4 commands · plm agent-memory

Long-term memory: one fact per entry, woven into a searchable web.

  1. Step 1 of 3

    Remember something

    A memory is one long-term fact the agent carries across every session. Every memory sits in one of two zones: PRIVATE (this agent's own, the default) or PUBLIC (--public, ships in the agent's releases so installs inherit it). Give it a kind (reference, scar, project, user…) so the index reads well, and seed --links to any related ids up front. Keep each memory one fact; link them into a web rather than writing one long file.

    plm agent memory add
    $ plm agent memory add "R2 presigned vs browser" --kind reference --body - --links mem_c84a,rul_82dd
    ✓ mem_0de66378538e42a0 (private)

    full form · plm agent memory add <title> [--kind …] [--body -|text] [--links a,b] [--public]

  2. Step 2 of 3

    Navigate the index

    One glance at everything the agent knows. Each row is zone-tagged [pub]/[priv]; the footer counts the split. A bare query searches across title, kind and body (memory velocity finds it by content), and --public / --private narrow to one zone. This is how an agent scans its own mind before deciding what it already knows.

    plm agent memory ls
    $ plm agent memory ls --private
    mem_0b6b8fff46e84c56 [priv] project PLMHub agents doctrine
    mem_380aaa01f2874020 [priv] user Edvard's velocity
    2 memories (0 public · 2 private)

    full form · plm agent memory ls [query] [--public|--private]

  3. Step 3 of 3

    Walk the web

    show reads a single memory in full and then resolves its neighbourhood: Links → (each outgoing id resolved to its title) and Linked from ← (every item that points back here). An id that no longer resolves shows as (external), so dangling links surface instead of hiding. This is the hop primitive: land on one memory, see everything connected, jump to the next id.

    plm agent memory show
    $ plm agent memory show mem_0de66378538e42a0
    mem_0de66378538e42a0 · reference · public
    R2 presigned vs browser
    Presigned R2 URLs fail browser fetch (CORS). Proxy through the API.
    Linked from ←
    mem_0b6b8fff46e84c56 PLMHub agents doctrine

    full form · plm agent memory show <mem_id>

Also in this chapter