Yash030's picture
feat: add Python plugin system, multi-agent connect CLI, and MCP tool expansions
26a284a
# forget worked examples
## 1. Delete a leaked secret
User: "Forget that note where I pasted the API key."
Search:
```json
memory_smart_search { "query": "api key", "limit": 20 }
```
Response:
```json
{
"results": [
{ "id": "abc12345", "sessionId": "7f3a9c21", "title": "Pasted staging API key",
"narrative": "STAGING_KEY=sk-live-..." }
]
}
```
Present and gate:
> Found 1 match:
> - `abc12345` (session `7f3a9c2`) "Pasted staging API key"
>
> Delete this memory? (yes/no)
After the user says yes:
```json
memory_governance_delete { "memoryIds": ["abc12345"], "reason": "user privacy request" }
```
Response:
```json
{ "deleted": 1 }
```
Present:
> Deleted 1 memory (`abc12345`).
## 2. Drop a whole session's observations
User: "Delete everything from the throwaway spike session."
Search, identify the session, then collect every memory id in it:
```json
memory_smart_search { "query": "spike prototype throwaway", "limit": 20 }
```
Response has 4 results all with `sessionId: c98f1100`. Show all four, get a yes,
then pass every id:
```json
memory_governance_delete {
"memoryIds": ["m1", "m2", "m3", "m4"],
"reason": "drop throwaway spike session"
}
```
Never send `{ "sessionId": "c98f1100" }`; the MCP deletes by memory id only.
## 3. User declines
User: "Actually, on second thought, keep them."
Do not call delete. Confirm:
> Understood, nothing deleted. The 4 memories from session `c98f110` are intact.