domains / families / agent-tooling / dispatch

dispatch

combined

Delegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code. Say 'check with codex' or 'ask gemini for a second opinion' and Claude runs the other agent, keeps a topic-aware session, and critiques the result. Delegate tasks to OpenAI Codex CLI and Google Antigravity CLI from Claude Code with topic-aware sessions

When to use

• Getting a second opinion from a different model family before merging
• Cross-checking Claude's analysis against Codex or Gemini
• Delegating a side task (research, review, image generation) to another CLI
• Triangulating a decision across multiple models and having Claude reconcile disagreements
• Resuming a prior delegation thread without restating context
• Use when you want a second opinion from a different model family before merging or shipping
• Use when you want to cross-check Claude's analysis against Codex or Gemini
• Use when you want to delegate a side task (research, review, image generation) to another CLI without leaving Claude Code

When not to use

• **agy has no read-only mode** -- it can edit files and run commands even when asked to analyze only. Dispatch requires explicit approval before agy delegation, mitigates analysis-only tasks by prompt-level constraint and git-status check a…
• **Topic-aware session IDs live in conversation memory only** -- they are lost on context compaction or when the conversation ends. If the mapping is lost, Claude asks or starts a fresh thread.
• **Cold start for agy can take 2-3 minutes** on the first call in a session (language server + auth spin-up). This is normal, not a hang.
• **Image generation quality depends on the underlying CLI's model** -- Codex uses gpt-image-2, Antigravity uses Nano Banana Pro. Neither supports native transparency.
• This skill does not replace environment-specific validation, testing, or expert review.

Skill page

Conflict

Both copies describe the same 'dispatch' skill for delegating to Codex and Antigravity CLIs, but the sickn33 copy adds material security and operational constraints that the davepoon copy lacks. Specifically, the sickn33 copy mandates explicit user approval before every delegation, requires passing prompts via stdin/temp files to prevent shell injection, and details limitations like agy's lack of read-only mode and session ID volatility. The davepoon copy is a cleaner, more concise version but omits these critical safety and implementation details. Crowning one would hide the other's valuable constraints or brevity.