Skip to content

Deleting a memory

PortalCLIIntermediate~10 min

Remove a memory you no longer need: it disappears from every list, search and agent that used it. It can't be brought back — not from the portal and not through the API — so be sure before you confirm.

For the model underneath — who owns which memory, and how that is meant to evolve — see Memory ownership and lifecycle.

Delete it in the portal

  1. Open the memory.
  2. Open its ⋯ menu and choose Delete memory — or go to its Settings tab and find Delete memory in the Danger zone at the bottom.
  3. Confirm with Yes, delete, or back out with Cancel.

If you don't see Delete memory, you aren't allowed to delete this one.

With the CLI, hadron memory rm <memory> does the same, under the same rules (add --yes to skip its confirmation prompt).

Who can delete which memory

Memory Who can delete it
A personal or private memory Its owner only.
Any other memory you own yourself (not an organization's) Its owner only.
An organization's memory Someone the organization allows to delete memories (the memory.delete permission).

The server enforces the same rules, so a request made some other way is refused too.

Two memories you can't delete directly

  • An agent's system memory — the one holding its conversation designs and prompts. It belongs to the agent: delete the agent instead (below), and the system memory goes with it.
  • A memory that hosts a Channel — for example, the memory holding an App's team chat. The delete is refused (MEMORY_HOSTS_CHANNEL) until the Channel is deleted first.

What deleting an agent or an App does

Deleting an agent — on the agent's page, Delete agent in the Danger zone, then Yes, delete — soft-deletes the agent and its system memory. Other memories the agent used are not touched; they belong to someone else and stay where they are. The agent's owner or an organization admin can do this.

Deleting an App — in the App's Settings, Delete app in the Danger zone — soft-deletes the App, and its API key stops working immediately. It does not delete any memory. Memories the App used stay, and you delete them separately if you want them gone. The App's owner or an organization admin can do this.

Soft delete, and no undo

Deleting a memory, an agent or an App is a soft delete: the row stays in the database, marked deleted, and stops appearing anywhere. For a deleted memory — including an agent's system memory — that also means its nodes and edges drop out of every list, search and agent memory picker. (Deleting an App doesn't touch its memories, so their content stays visible.)

There is no undelete. The portal has no restore, and the API has no restore operation for a deleted memory, agent or App. Deleted memories are also not purged automatically; they remain in the database, hidden.

Where this is heading

Hadron's ownership model is moving towards memories that belong to an agent or an App and go when their owner goes. Today, only an agent's system memory follows its owner; deleting an App leaves its memories in place. See Memory ownership and lifecycle.

See also