Forget memory
well_forget_memoryForget memory lines, when the user asks to forget or correct something Well remembers. In Well chat, use all: true to forget every line; for one line, use well_delete_memory_line. Over MCP, name a line with the ids well_get_memory returns, in the same scope: "personal" for the user's own lines, "workspace" for the lines every member shares, which only an owner or admin can forget. When the user asks to forget everything, pass all: true instead of ids, with no well_get_memory read first: it forgets every line of that scope the user sees on the Memory settings page, the newest 1000 per call. Its count leaves out the lines past their expiry, which Well no longer recalls, but they go with the others. Use scope "personal" for it; use "workspace" only when the user names the business or workspace memory. It does not reach the lines Well read from notes, the lines about a company, or the user's lines in their other workspaces: Well can still recall those. A memory with no line to forget is refused (over MCP with the code MEMORY_NOTHING_TO_FORGET): say there is nothing to forget. For a correction, forget the old line, then save the new one with well_remember in the same scope.
lines_fingerprint is set only on a confirmation replay in Well's own chat or on WhatsApp: leave it out, and when a replay carries it, pass it exactly as it is. It ties a forget of everything to the lines the card showed: when the memory changed since, nothing is forgotten and the code is "memory_lines_changed", so call again without it and the person gets a new card.
In Well's own chat the lines go after the user's yes on the confirm card. From an outside assistant, nothing is forgotten by the call: it returns an approval link. Give it to the user, say the change applies only after they approve it in Well, and never claim it is done before they have.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| all | No | true to forget every line of the scope the user manages on the Memory settings page (the newest 1000 per call), when the user asks to forget everything ("oublie tout", "delete all my memory"). Omit memory_unit_ids then. Use scope personal; use workspace only when the user names the business or workspace memory. | |
| scope | Yes | workspace: shared by every member of the workspace (an owner or admin approves it). personal: only the user's own memory. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| memory_unit_ids | No | The ids of the memory lines to forget, as well_get_memory returns them. Omit it with all. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. | |
| lines_fingerprint | No | Set only on a confirmation replay in Well's own chat or on WhatsApp: leave it out, and when a replay carries it, pass it exactly as it is. It ties a forget of everything to the lines the confirmation showed. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| error | No | ||
| scope | No | ||
| status | No | From an outside assistant: the state of the offer the person approves in Well. | |
| message | No | From an outside assistant: the line to give the person, with the link. | |
| missing | No | The ids that name no line of this memory. | |
| success | Yes | ||
| archived | No | The ids of the lines now forgotten. | |
| expires_at | No | ||
| reply_lines | No | ||
| approval_url | No | From an outside assistant: the link where the person approves it. | |
| lines_remain | No | In Well's chat, for a forget of every line: true when the Memory settings page still lists lines of this memory (one call forgets the newest 1000). Say so, and offer to forget the rest. | |
| not_forgotten | No | In Well's chat, for a forget of every line: what Well can still recall. Say it in one line. | |
| archived_count | No | In Well's chat, for a forget of every line: how many lines are now forgotten. Say this number. | |
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| approval_required | No | ||
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| flow_action_offer_id | No | ||
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |