Delete a memory or a folder
Deletes the memory, or every memory in the folder the path names, each with a version that records the delete. Versions stay with the Agent.
AuthorizationBearer <token>An application key of the Tenant (PUT /v1/tenant/keys/{keyId}), or Studio's key, derived from the admin key. With Nylorun-Subject and Nylorun-Scopes, it acts for that person, narrowed to those scopes. Never accepted from a browser (Origin).
agentId*stringThe Agent id, percent-encoded
path*stringThe memory's path under /memories, percent-encoded: conventions%2Frelease.md is /memories/conventions/release.md
Nylorun-Protocol*stringThe protocol version, 18
Nylorun-Subject?stringThe person an application key acts for
Nylorun-Scopes?stringThe subject's space-separated scopes; required with a subject
What was deleted
application/json- response
path*stringdeleted*integer0 <= valueimport { createClient } from "@nylorun/agents";const client = await createClient();await client.agents.memories.delete("users/alice/assistant", "conventions/release.md");{ "path": "string", "deleted": 0}Write a memory PUT
Creates the memory or replaces its content, as the `memory` tool's `create` does, and records a version with the caller as its actor. This is how an app seeds an Agent's memory. With `contentSha256` the write applies only while the memory still has that content (`""`: only while no memory has the path); otherwise `409 memory_conflict` with the current memory. The path ends in `.md`; the Runtime limits `memoryBytes` (`413`) and `memoriesPerAgent` (`409 limit_exceeded`) hold.
List an Agent's memory versions GET
Every change to its memories, newest first: the operation, the path (a rename's names its old one), and who made it: `agent:<manifest>@<version>` with the session, turn and trigger run of a turn's write, or the API caller. `path` keeps one memory's.