orchestrator

You can restrict the main thread to read-only operations by enabling orchestrator mode, which blocks main-thread Edit, Write, and MultiEdit tools while delegating file modifications to subagents via Task(). Run /orchestrator on from your project root to activate it instantly.

Yes, you can delegate file writes to subagents without restarting by using the orchestrator toggle script. Running /orchestrator on or /orchestrator off immediately switches the delegation mode and restricts or restores main-thread write capabilities in real-time.

Orchestrator mode enforces safety guardrails that protect sensitive files like .env and block dangerous recursive rm bash patterns. The hook intercepts classified write operations, ensuring unauthorized or destructive commands are prevented before execution by the subagent.

When the pre tool use hook blocks a tool call, orchestrator mode provides built-in recovery instructions to help you route the blocked operation correctly. You must delegate the specific file write or edit task to a subagent using Task() to bypass the main-thread restriction.

Yes, orchestrator mode blocks write-style shell operations in addition to standard file editing tools. The pre tool use hook classifies and intercepts bash write patterns, restricting the main thread to safe reads while ensuring all modifications are delegated to subagents.

You should avoid using a read-only main thread if your workflow requires rapid, direct edits from the primary thread without subagent overhead. Since orchestrator mode strictly blocks all main-thread write operations, it is best suited for complex tasks rather than quick, isolated file modifications.