add-codex

Replace Claude Agent SDK with Codex for planning, tool orchestration, and session resume.

5|Updated Apr 2, 2026

Search Tags:#codex #agent #orchestration #session #provider #app-server

Ready to run

npx skills add https://github.com/thmtz/nanoclaw-fleet --skill add-codex-thmtz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-codex
Source: https://github.com/thmtz/nanoclaw-fleet/tree/main/.claude/skills/add-codex
Command: npx skills add https://github.com/thmtz/nanoclaw-fleet --skill add-codex-thmtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex app-server and CLI-based provider replace Claude Agent SDK for planning, tool orchestration, and session resume, enabling a robust, per-group agent provisioning workflow within NanoClaw fleets.

Core Features & Use Cases

Codex-based provider integration: plugs Codex CLI and AppServer into the agent runner for deterministic turns.
Per-group and per-session agent_provider control: operates isolation across groups and sessions.
Session resume and MCP tool access: maintains state across turns and enables multi-turn tool calls.

Quick Start

Run a test group with agent_provider set to codex to verify a complete end-to-end turn cycle.

Frequently Asked Questions about add-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I replace Claude Agent SDK with Codex for agent orchestration?▼

You can replace the Claude Agent SDK by configuring Codex as your agent provider to handle planning, tool orchestration, and session resume. This integration leverages the Codex CLI and AppServer for deterministic execution turns.

What is per-group agent provisioning in NanoClaw fleets?▼

Per-group agent provisioning isolates agent provider configurations across different groups and sessions. Setting agent_provider to codex ensures containerized session management and secure token handling within NanoClaw fleets.

How do I test a Codex agent provider end-to-end?▼

Run a test group with the agent_provider parameter set to codex. This verifies a complete end-to-end turn cycle, validating Codex CLI and AppServer integration for multi-turn tool calls and session resume.

Does Codex app-server integration support session resume and state isolation?▼

Yes, Codex app-server integration maintains state across turns for session resume. It provides per-session isolation and enables multi-turn MCP tool calls within containerized session management environments.

When should I use Codex instead of the Claude Agent SDK for tool orchestration?▼

Use Codex when you need native MCP tool access, app-server integration, and per-group agent provider control. It replaces the Claude Agent SDK to enable robust, deterministic agent provisioning workflows.

Can I control agent providers per session using Codex CLI?▼

Yes, you can control agent providers per session and per group using Codex CLI. This approach ensures session isolation, secure token handling, and consistent state management across multi-turn interactions.