pause_persistence
Pause write operations across the MCP server for benchmarking, AB testing, or exploration. All write tools return dry-run responses, preventing database writes.
Instructions
Pause write operations on this MCP server for an opt-in TTL window. While paused, every write tool — store, archive_episode, update_memory, delete_memory, delete_episode, delete_agent_data, lock_memory, unlock_memory, update_profile, import_memories, merge_memories, calibrate_threshold, set_recall_precision — returns a no-op response carrying persisted: false, dry_run: true and a reason (with the TTL remaining) instead of writing to the database. persisted: false is the authoritative signal: branch on it, not on an id. Where the success shape has an id, it reads "no-persist" (store, archive_episode); action-specific id keys (deleted_id / updated_id / locked_id / unlocked_id / episode_id) are blanked to null so a truthy echo cannot read as success. migrate_channel_axis is gated differently — it is forced to dry_run and reports repairs_skipped rather than returning a skipped-response, so it carries no persisted key. check_health and deep_check are not blocked but downgrade to fix=false (they answer with repairs_skipped: true). Read tools (recall, list_*, get_profile, etc.) still answer normally, except that recall suppresses its recall_count / last_recalled_at bump — a write that would otherwise move ranking state during a paused session. The pause is PROCESS-WIDE, not per-session (response scope: "process"): the flag is one module-global on the server process. On a streamable-HTTP deployment a single process serves every connected client, so pausing here silences writes for ALL connected sessions until resume or TTL elapse — and the other sessions get no signal. Under stdio (one process per client) it is effectively session-scoped. This affects only this MCP server (cpersona); call cscheduler's pause_persistence too if you want both paused. Use for benchmarking, AB testing, or ephemeral exploration where memory contamination must be avoided. Default TTL: 1800 seconds (30 minutes); upper bound: 86400 seconds (1 day).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ttl_seconds | No | TTL until automatic resume. Min 1, max 86400 (clamped). Default 1800. |