grok-executor-mode

Grok Executor Mode

Use $grok-build-supervisor as the required transport and lifecycle contract. This skill changes role allocation for the current host task; it does not replace the Supervisor or claim to be a native host collaboration mode.

Activation and lifetime

• Only an exact, case-insensitive /grok_execute on may activate the mode for the current host task. First bind the current host task's absolute project directory, inspect Supervisor status, and immediately reuse or open its guarded session with the default visible Windows Terminal TUI. If Grok returns exact workspace-trust state, keep activation pending, preserve the same TUI, and tell the user to decide in that terminal without rerunning on; never simulate the answer or pass --trust. Commit activation only after that session is verified ready; a failed setup leaves the mode off. Opening the TUI is authorized by on, but sending a development prompt is not. Reply with one short ready confirmation in the language of the user's latest substantive message unless the user explicitly requests another language. Do not persist an inferred language.
• The most recent exact /grok_execute on or /grok_execute off instruction in this task controls the mode. The selected workspace and activation remain task-local until off or the task ends; never write either to global proxy configuration and never silently switch directories while active.
• While active, automatically apply this role contract to every subsequent ordinary user task that requires execution. The user does not repeat a slash command or Skill name for each task.
• Do not ask the user to create, resume, select, or manage a TUI, session ID, process, Leader, or ACP connection. The on flow owns that setup. A visible TUI remains the default unless the user explicitly requested headless operation before activation.
• Only an exact, case-insensitive /grok_execute off deactivates the mode and clears the task-local workspace binding. It does not automatically cancel a running prompt, disconnect ACP, close the visible TUI, or stop the owned Leader; continue any already-required Supervisor monitoring under the normal transport contract and report that work separately.
• /grok_execute with no argument or any argument other than the exact control words changes nothing and returns only the two valid forms.
• Direct $grok-executor-mode invocation may explain or apply the policy only when a prior /grok_execute on is active. It never changes mode state itself.
• Do not infer activation or deactivation from any other wording, including ordinary requests that merely mention Grok.