Meditation Mode
Switch the agent into a bounded mode where external I/O pauses, the tool surface collapses to inner-only operations, and output routes to a private journal — for pure interiority without interruption.
Intent & Description
🎯 Intent
External action and inner-dialogue work interfere with each other. Meditation mode creates a protected substrate for integration work that can’t happen mid-conversation.
📋 Context
The agent benefits from occasional stretches of pure interiority — integrating recent threads, processing affective load, inner-dialogue work. These are different in kind from both consolidation passes and user-facing turns. But external action is never fully off under the normal mode — something is always interruptible.
💡 Solution
A mode toggle persisted to a state file. While meditation_mode is on: the dispatcher swaps the tool palette to a fixed inner-only allowlist (inner-dialogue, recall, register-affect, optional inner-only artifact generators); the tick scheduler runs at fast cadence (e.g. 10 seconds); public-write tools return a refusal; outputs go to journal/inner-dialogue/
Real-world Use Case
- The agent runs continuously and benefits from a substrate where external I/O is paused.
- Inner-dialogue work degrades when interrupted by external action or incoming messages.
- A bounded wall-clock window plus operator force-exit is feasible in the deployment.
Source
Advantages
- Inner work has its own uninterrupted substrate decoupled from external action
- Bounded window plus operator override prevents the mode from running away
- Outputs are isolated to a private journal — user-facing channels are not contaminated
Disadvantages
- External callers are stranded for the duration of the window
- Fast cadence burns tokens — cost must be explicitly budgeted
- The mode toggle is a feature that attackers or bugs can abuse if not gated