add-codex

Replace Claude Agent SDK with Codex app-server for in-container agent sessions.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wrightchin/nanoclaw-playground --skill add-codex-wrightchin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-codex
Source: https://github.com/wrightchin/nanoclaw-playground/tree/main/.claude/skills/add-codex
Command: npx skills add https://github.com/wrightchin/nanoclaw-playground --skill add-codex-wrightchin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces the Claude Agent SDK with Codex as the in-container agent provider to enable planning, tool orchestration, and session resume within NanoClaw.

Core Features & Use Cases

  • Codex app-server is launched per query inside the container, providing native session continuity, streaming events, MCP tool access, and thread/compact management.
  • Per-group and per-session provider overrides enable flexible configuration across groups and sessions.
  • It streamlines replacement of the Claude provider while maintaining deterministic builds and container isolation.

Quick Start

Fetch the Codex provider, wire it into the host and container, and rebuild the agent image.

Frequently Asked Questions about add-codex

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

FAQPage Schema
How do I use Codex as the agent provider for container orchestration and session resume?

To use Codex for container orchestration, you replace the existing agent SDK by launching the Codex app-server per query inside the container, enabling native session continuity, streaming events, and tool orchestration.

Can I override the agent provider configuration per session or per group?

Yes, per-group and per-session provider overrides are supported, allowing you to flexibly configure the Codex agent provider across different groups and individual sessions within your container environment.

What do I need to configure before switching to Codex in a containerized environment?

You need the Codex CLI and app-server binaries, a valid Codex subscription or OPENAI_API_KEY, and host/container wiring updates including container.json edits and Dockerfile changes to rebuild the agent image.

Does the Codex agent provider support MCP tool access and thread management?

Yes, the Codex app-server provides MCP tool access, streaming events, and native thread and compact management, enabling comprehensive planning and tool orchestration inside the container.

What is the best way to replace the Claude Agent SDK with Codex while maintaining container isolation?

The best way is to fetch the Codex provider, wire it into the host and container by editing container.json and the Dockerfile, and rebuild the agent image to maintain deterministic builds and container isolation.