grok-build-delegate

Grok Build delegate

Bridge to the local, subscription-authenticated Grok Build CLI (xAI). Use it to get an independent second opinion, an adversarial review, or a delegated investigation without leaving the Codex or Claude Code session. This is a separate review/task channel, not a model swap for your own work.

Delegation policy

Delegate when the user explicitly asks for Grok, Grok Build, grok-4.5, a second opinion, or an external/adversarial review. Also delegate selectively when all of these hold:

• the task has a clear scope and acceptance condition;
• Grok can work independently without secrets or missing product judgment;
• the host agent can verify the result with a diff, tests, or concrete evidence.

Good implicit candidates include reviewing a diff, investigating a focused failure, implementing an already-written plan, and mechanical or repetitive edits. Keep fuzzy product work, architecture, UX/copy judgment, security-sensitive work, and final acceptance in the host agent. Do not delegate merely to avoid doing ordinary work.

Routing

• Setup or health check → grok_build_setup. Run it first when anything looks misconfigured; it reports CLI availability, auth, model, fallback, and state storage.
• Quick question or second opinion → grok_build_prompt. Foreground, strictly read-only.
• Current web/X research → read-only grok_build_task with write: false, background: true, and timeout_ms: 180000 or longer. Explicitly ask Grok to use web_search / web_fetch, return direct source URLs, and distinguish official or first-party posts from community commentary. Poll grok_build_status, then read the terminal record with grok_build_result.
• Code review → grok_build_review. Pass scope (working-tree, branch, or repo) and base_ref for branch/repo; set adversarial: true to challenge assumptions.
• Investigation or a longer task → grok_build_task. For long runs set background: true, then poll grok_build_status and read grok_build_result when it finishes. Use grok_build_cancel to stop a running job.
• Bounded implementation → write-enabled grok_build_task. Leave shell disabled when Grok can implement with native file tools alone. Add allow_bash: ["test"] only for one focused test or type-check command, or allow_bash: ["render"] only for one short render command. Do not ask Grok to run the full acceptance suite; the host agent performs final verification.
• Image generation or editing → grok_build_image. It always uses grok-4.5. Pass reference_images as absolute local paths for edits and for any named real person.
• Video generation → grok_build_video. It always uses grok-4.5. Pass an absolute source_image when available; otherwise Grok creates a first frame, then animates it. Duration must be 6 or 10 seconds, and resolution must be 480p or 720p.
• Speech / voiceover / TTS generation → grok_build_tts. This is a direct call to xAI /v1/tts using the local Grok Build OIDC subscription login from ~/.grok/auth.json; it does not need or use XAI_API_KEY. Pass the spoken text, an ISO language code (zh, en, etc.), and optionally voice_id (eve is the default; ara, leo, rex, sal, or a custom voice ID can be used). If supplied, output_path must be an absolute .mp3 path inside cwd.