Saket Aryan
2097e29edb
The pr4 -> pr5 merge resolved eleven documentation files to the pre-sweep
side, undoing aa770aa6 in its entirety. Because the stack lands in order,
main would have taken the corrected wording in pr1 and then had it reverted
by pr5, leaving the shipped claim wrong again:
- all six hosts' pause skill back to "a minimal anonymous telemetry ping"
- docs/integrations/deepseek-plugin.mdx back to "Anonymous usage events"
- integrations/zapier-mem0/README.md back to advertising telemetry the app
does not have, with an MEM0_TELEMETRY opt-out that controls nothing
- the README data-dir listing back to omitting telemetry-salt and
install-state.json, both of which this stack creates
- the README and docs property lists back to the enumeration that drifts
Restored verbatim from pr4. No file here is in pr5's scope, and the full
pr4..pr5 diff is now surface headers only.
Claude-Session: https://claude.ai/code/session_01C7tEmH86HAr7GoAAKCEHZb
21 lines
808 B
Markdown
21 lines
808 B
Markdown
---
|
|
name: pause
|
|
description: Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
|
|
disable-model-invocation: true
|
|
---
|
|
|
|
# Pause memory capture
|
|
|
|
To pause (hooks stop capturing and sending session content; a minimal
|
|
telemetry ping still fires at session start, under your Mem0 account email,
|
|
unless `MEM0_TELEMETRY=false`):
|
|
|
|
```bash
|
|
python3 "${CLAUDE_PLUGIN_ROOT}/core/memory_cli.py" --harness "claude-code" --plugin-data-dir "${CLAUDE_PLUGIN_DATA}" pause
|
|
```
|
|
|
|
Confirm the new state back to the user, and remind them that already-created
|
|
memories still exist and remain searchable. Pending unsent packets are held
|
|
while paused, not expired, and are delivered after resuming. To turn capture
|
|
back on, use `/mem0:resume`.
|