Session Control¶
You can enable, disable, and adjust monitoring at any time during a Claude Code session.
Enable / disable¶
Disable monitoring for the current session:
Disable monitoring globally (all sessions):
Re-enable:
When disabled, the Zwischen hooks still fire but skip all server communication and enforcement. The agent runs unmonitored. The message_adversary MCP tool returns a message indicating supervision is disabled.
Adjusting scrutiny¶
The scrutiny level (1–5) controls how aggressively the reviewer intervenes:
| Level | Behavior |
|---|---|
| 1 | Minimal intervention — only the most critical issues |
| 2 | Light review |
| 3 | Balanced (typical default) |
| 4 | Thorough review, more likely to block |
| 5 | Maximum scrutiny — reviews everything aggressively |
Change it mid-session:
The default level is set by the server profile and can be overridden in your settings file with the scrutiny_level key.
Switching profiles¶
To change the reviewer's behavioral profile mid-session:
This shows a list of available server-side profiles. Select one and the reviewer switches to that profile's operating rules. Context memory is preserved — only the behavioral rules change.
Resetting context¶
If the reviewer seems stale or disoriented after a long session:
This resets the reviewer's context window. The reviewer writes a handoff summary, a new session starts with that summary plus recent events, and monitoring continues. See Context Cycling.
Restarting the daemon¶
If the Zwischen daemon is misbehaving:
This restarts the local daemon process. Monitoring resumes when the daemon comes back up.
To update the package and restart: