OpenClaw Codex App Server

Context

openclaw-codex-app-server is a plugin that lets OpenClaw route conversation traffic to existing Codex sessions. The goal is simple: keep using your local Codex and local auth state while getting the interaction model you want inside OpenClaw-managed chat channels.

I use it to move between threaded, stateful Codex workflows without re-authenticating per tool or duplicating context.

Source and installation

• NPM package: https://www.npmjs.com/package/openclaw-codex-app-server
• Public repository: https://github.com/pwrdrvr/openclaw-codex-app-server
• OpenClaw plugin install command:
  • openclaw plugins install openclaw-codex-app-server
• Relevant docs: https://docs.openclaw.ai/tools/clawhub

What it does

• Binds chat context to existing Codex threads so input can be sent as continuation messages.
• Supports project/thread picking and context-aware continuation (/cas_resume, /cas_status, /cas_review, /cas_stop).
• Handles permission-bound actions and status reads while preserving workspace/thread boundaries.
• Keeps command and thread control in chat workflows (model switching, approvals, stop/compact, rename, etc.).

Technical details

• Built as an OpenClaw extension using the plugin lifecycle and compatibility constraints in openclaw.plugin.json.
• Uses ws-backed transport surfaces for protocol interactions and action rendering.
• Includes robust parsing for request payloads and prompt shaping so thread and user-state flows stay clean under load.
• Includes test and TypeScript tooling (vitest, tsc) for protocol confidence.

Why this project is here in my portfolio

This plugin is a practical integration project: it connects local-first tooling habits with conversational operations. It reduces the impedance mismatch between chat-driven agent control and long-running Codex sessions by making the bridge explicit and predictable.