workflow.md you can copy, validate, and
dispatch. Extend any of them with blocks from Snippets;
check field meanings in the Workflow Schema.
Choosing a method
Themethod field selects how a runtime is driven. Rules of thumb:
| Method | Choose when | Trade-off |
|---|---|---|
api | You want stateless turns, structured output, tight latency control, or server-side features (e.g. OpenAI Responses/Realtime/Operator). | You manage context/state in the workflow; no vendor-native agent loop. |
sdk | You want the vendor’s full agentic loop — native tool calling, hooks, sessions, thinking budgets (e.g. Claude Agent SDK, OpenAI Agents SDK, GenAI SDK). | Heavier per-turn; vendor loop semantics apply. |
cli | The capability lives in a local agent binary (Claude Code, Codex CLI, Antigravity) — local file edits, sandboxed shell, repo-scale work. | Requires local install; dispatch_path is local. |
mcp | You are bridging an external MCP server’s tools into the run. | Tool-surface only. |
desktop_app | Driving a desktop surface (voice shell, UI automation). | Desktop session required. |
gemini-genai-sdk (sdk); repo implementation
→ anthropic-agent-sdk (cli or sdk); independent code review →
openai-codex-sdk (cli); cheap structured calls → openai-responses-api (api);
voice → openai-realtime-api (api) or local-voice; computer use →
openai-operator (api); offline/private → local-llm (api).