← ClaudeAtlas

agent-codex-gatelisted

Pattern for spawning subagents whose work must receive an evidence-backed, unconditional Codex review through the local llm-cli-gateway stdio MCP server. Use when parallel implementation tasks need an independent Codex quality gate.
verivus-oss/llm-cli-gateway · ★ 15 · AI & Automation · score 80
Install: claude install-skill verivus-oss/llm-cli-gateway
# Agent + Codex Gate Pattern Spawn subagents for independent implementation work, then make each one obtain an unconditional Codex verdict before accepting its result. A Codex-only gate is not a substitute for a required cross-LLM review. ## Required Transport and Review Contract Use the local stdio gateway only. In Codex, the tools normally appear as mcp__gtwy__codex_request, mcp__gtwy__codex_request_async, and mcp__gtwy__llm_job_*. Other MCP clients may display the short names. Do not run the codex CLI directly for a review request. For every mandatory review: 1. Omit model unless the caller explicitly selected a model. 2. Pass approvalStrategy: "legacy". Gateway-managed approval is Claude-only; Codex rejects mcp_managed and ignores approvalPolicy. 3. Use sandboxMode: "read-only" for normal inspection. Use sandboxMode: "workspace-write" only when the reviewer must produce write-producing build or test artifacts. Do not use fullAuto; it is a deprecated shorthand for workspace-write. 4. Require the terminal JSON verdict: `APPROVED_UNCONDITIONALLY`, `CHANGES_REQUIRED`, or `BLOCKED_EXTERNAL`. 5. Do not set a review round, turn, token, price, cost, or wallclock limit. The configured idle-timeout safeguard is for a process that produces no output, not a completion deadline. 6. Continue until Codex returns explicit, evidence-backed `APPROVED_UNCONDITIONALLY`. A conditional verdict, residual finding, malformed response, inability to verify, timeout,