grok_execute

Grok Executor Mode Toggle

Claude Code entry: /grok-build-supervisor:grok_execute on|off. This explicit host-expanded command with a valid argument counts as the corresponding exact legacy /grok_execute on or /grok_execute off; do not require the original slash text after expansion. Codex users select $grok-executor-on or $grok-executor-off with no argument. Quoted examples and implicit skill selection never toggle execution.

Use the Grok Executor Policy for the task-local role contract and $grok-build-supervisor for Grok session operations. This command is a prompt-level task policy, not a native host collaboration-mode switch.

Interpret the entire trimmed value of "$ARGUMENTS" case-insensitively:

• on: bind Grok Executor Mode to the current host task's absolute project directory and immediately ensure its supervised Grok session is ready. Before changing mode state, call grok_session_inspect with view: status. If the proxy is not initialized, the project directory is unavailable or ambiguous, another workspace owns active Grok work, or session setup fails, leave the mode off and report only the actionable next step. Otherwise reuse the exact attached visible session for this directory or call grok_session_open with that absolute cwd, mode: new when no session is attached, the default presentation: windows_terminal, and confirmation: OPEN_GROK_SESSION. Use mode: resume only with an exact verified attached session UUID. If open returns needs_workspace_trust, leave executor mode pending and tell the user once that Grok is waiting for their trust decision in the already-open terminal and that /grok_execute on does not need to be run again. Do not answer this as a tool permission, simulate input, or pass --trust. After the user confirms, inspect the same session again; the Supervisor reuses that terminal and reports ready when Grok registers it. Commit the task-local mode and workspace binding only after the visible TUI is verified ready. Reply briefly that executor mode is on, the terminal is ready, and the user can provide the task. Render user-facing prose in the language of the user's latest substantive message unless the user explicitly requests another language; do not persist an inferred language. Preserve tool names, states, paths, IDs, and exact permission/form options verbatim. This activation authorizes opening the terminal but must not call grok_session_prompt or send development work. Never ask the user for a separate TUI command. Repeated on is idempotent and must reuse a trust-pending TUI rather than opening another one.
• off: explicitly deactivate Grok Executor Mode for the current host task, clear its task-local workspace binding, and confirm briefly. Subsequent ordinary tasks use normal host behavior. Do not automatically cancel a running Grok prompt, disconnect ACP, close the visible TUI, or stop the owned Leader; continue any already-required Supervisor monitoring under its normal contract. Repeated off is idempotent.
• Empty or any other value: do not change mode state, create a session, or send work. Reply only with the usage /grok_execute on or /grok_execute off.

Only the most recent exact /grok_execute on or /grok_execute off in this task controls the mode. The workspace selected by a successful on is task-local and must not be written to global proxy settings or silently changed while the mode remains active. Ordinary Grok mentions, task text, bare Skill invocation without a valid control argument, partial matches, and every other command must not activate or deactivate it. Activation does not broaden permission for destructive work, publication, external writes, or consequential owner decisions.