Skip to content

memory_delete

Managementcatalog

Clear Memory Layer

Not in the default tool list

This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_delete. To list every tool directly, connect with ?toolsets=full.

Clear one entire Scenario instruction or memory layer. Destructive and irreversible through this tool. Scopes: user_instructions (personal rules, 20480 UTF-8 bytes), team_instructions (shared team rules, 51200), project_instructions (shared project rules, 51200), user_memory (personal facts across projects, 30720), project_user_memory (private facts for this user in this project, 30720). OAuth only. Personal layers need neither tenant ID; team instructions need team_id; project layers need both team_id and project_id. The API checks membership; team instruction writes need a team admin, project instruction writes need a project or team admin. Use only when the user wants this whole layer forgotten or reset. To forget one fact, read the layer, remove that fact and use memory_set to preserve the rest. Never move forgotten facts into another layer. Args: scope, applicable explicit team_id/project_id, response_format. Returns: { scope, cleared: true, size_bytes: 0, updated_at: null }. Sends null content to hard-delete the saved record. Example: scope="project_user_memory" with the chosen team_id/project_id to forget all of this user's memories in that project. Don't use to clear all layers at once, remove a single preference, or edit another user's memory. Instruction caches in the Scenario assistant may take up to one hour to expire.
destructiveidempotentopen-world

Parameters

NameTypeRequiredDescription
team_idstringTeam ID. Required if user belongs to multiple teams.
project_idstringProject ID to scope the operation to.
response_formatenum(json | markdown)jsonOutput format: 'json' for structured data, 'markdown' for human-readable text.
scopeenum(user_instructions | team_instructions | project_instructions | user_memory | project_user_memory)Layer to access. user_* belongs to the signed-in user; project_user_memory is private to that user in the project. team/project_instructions are shared rules. Project layers need both team_id and project_id; team_instructions needs team_id. Personal layers need neither.