delegate

Raw user request: $ARGUMENTS

Execution mode:

• If the request includes --no-subagents, do not invoke the grok:grok-delegate subagent. Run grok-companion.mjs task directly via Bash instead (see Direct companion flow below).
• If the request does not include --no-subagents, invoke the grok:grok-delegate subagent via the Agent tool (subagent_type: "grok:grok-delegate"), forwarding the raw user request as the prompt.
• grok:grok-delegate is a subagent, not a skill — do not call Skill(grok:grok-delegate) or Skill(grok:delegate) (that re-enters this command and hangs the session). The command runs inline so the Agent tool stays in scope; forked general-purpose subagents do not expose it.
• The final user-visible response must be Grok's output verbatim.

Subagent path (default):

• Always invoke the grok:grok-delegate subagent in the foreground (do not use the Agent tool's run_in_background). The subagent runs Grok and returns the answer, so the result is delivered to you in-band.
• Default (and --wait): the subagent runs grok-companion.mjs task in the foreground and returns Grok's full answer. This is the right choice for almost every delegation. It is bounded by the Bash tool's ~10-minute limit; if a task is likely to run longer, use --background.
• --background: the user is opting into a long-running or fire-and-forget run. The subagent forwards --background to task, which launches a detached worker and returns a job id immediately (not the answer). Surface that job id and tell the user to retrieve the result with /grok:status <id> and /grok:result <id>. --background survives arbitrarily long Grok runs.
• --wait and --background are execution-mode flags — strip them from the natural-language task text. --wait is the default and is not passed to task; --background is passed through to task.
• --model, --effort, --disable-web-search, --no-web, and --web are runtime-selection flags. Preserve them for the forwarded task call, but do not treat them as part of the natural-language task text. Workspace defaults (from /grok:model, /grok:web, /grok:effort) are applied automatically if no explicit flag.
• Effort can also be requested in natural language. Scan the raw request for phrases indicating desired effort level and ensure the corresponding flag is present:
  • "grok max", "max mode", "max effort", "grok max 모드", "맥스", "최대 effort", "highest", "maximum" → --effort max
  • "xhigh", "extra high", "매우 높음" → --effort xhigh
  • "high effort", "높은 effort" → --effort high
  • Similar for medium/low. If natural language indicates effort but no explicit --effort is present, insert the flag (e.g. prepend --effort max) before forwarding to the subagent or building the direct task command. Prefer any explicit --effort over inferred.
• Advanced Grok features: Dedicated commands exist for convenience (/grok:image, /grok:edit-image, /grok:video, /grok:edit-video, /grok:vision, /grok:tts, /grok:stt). You can still use natural language in this command. Detect common patterns and forward accurately:
  • Image: "generate image", "grok generate image", "create image of", "grok image"
  • Edit image: "edit image at PATH", "modify image", "grok edit image ./file.jpg to ..."
  • Analyze/vision: "analyze image at PATH", "grok vision", "describe image ./screenshot.png", "grok analyze image"
  • Video: "generate video", "grok generate video", "edit video ./clip.mp4"
  • File upload: "upload file", "grok upload file at ./report.pdf"
  • Brainstorm/search: "brainstorm ideas", "grok search for", "grok search x for"
  • Code/calc: "run code", "calculate", "grok calculate" Always preserve exact file paths mentioned (e.g. ./photo.jpg, /absolute/path/video.mp4). Do not rewrite or summarize paths.
• Permission and file handling guidance (important for Claude to manage safely):
  • When the request touches files/folders (read for vision/analysis, write for edit/generate), keep paths verbatim.
  • For read-only analysis/vision/describe: Forward as-is; Grok binary will attempt read access based on current user/shell permissions.
  • For modifications/generation that may save files: Ensure write-capable delegation (default behavior adds --write). If user might not want auto-approve, consider --no-subagents or note it.
  • If permission issues are likely (e.g., restricted dirs, read-only workspace), include explicit notes in the forwarded prompt like "Note: access may require user approval for file X".
  • Claude (main session) should handle approvals for the initial delegation Bash call. For internal Grok approvals during execution, they will appear in the returned output.
  • Prefer absolute paths when possible for reliability, but respect user's provided relative paths.
  • Never assume files are accessible; if the task involves specific files, the prompt must contain the paths so Grok can reference them.
• Web search is disabled by default for this workspace. Pass --web only when the user explicitly wants web search for this run. Pass --no-web to force-disable even when the workspace default is on.
• If the request includes --resume, do not ask whether to continue. The user already chose.
• If the request includes --fresh, do not ask whether to continue. The user already chose.
• Otherwise, before starting Grok, check for a resumable delegate thread from this Claude session by running: