OpenClaw Codex App Server Lite

Minimal OpenClaw plugin for Telegram and Feishu Codex thread binding and message relay.

This plugin lets a Telegram or Feishu conversation bind to a local Codex thread, then continue sending normal messages into that thread through codex app-server.

The latest version supports both Telegram and Feishu. Feishu support is the main focus of this update.

Compatibility

• Adapted for the latest OpenClaw 2026.4.5
• Version 0.0.1 was verified against OpenClaw 2026.4.5
• Supports Telegram and Feishu

Install

From npm:

openclaw plugins install --dangerously-force-unsafe-install @mallocfeng/openclaw-codex-app-server-lite

From a local checkout:

openclaw plugins install --link "/absolute/path/to/openclaw-codex-app-server-lite"

After installing, updating, or relinking the plugin, run:

openclaw gateway restart

so OpenClaw reloads the plugin code.

Uninstall

openclaw plugins uninstall openclaw-codex-app-server-lite
openclaw gateway restart

Commands

• /codex_start: list threads, create a thread, or bind the current Telegram or Feishu conversation
• /codex_stop: detach the current Telegram or Feishu conversation from the bound Codex thread

Config

• command: Codex CLI command to run, defaults to codex
• args: extra args passed to codex app-server
• defaultWorkspaceDir: default workspace used when creating or resuming threads
• defaultModel: preferred model for new threads
• inheritHostAuthEnv: when true, forward host auth env vars like OPENAI_API_KEY into codex app-server

inheritHostAuthEnv defaults to false. That is intentional. On machines where OpenClaw uses provider env vars like OPENAI_API_KEY=ollama, forwarding the host auth env into Codex can override Codex OAuth login and break normal thread replies.

Latest Update

Version 0.0.1 includes the OpenClaw 2026.4.5 compatibility refresh, the auth-environment fix for post-bind message failures, and the new Feishu conversation flow.

The main focus of this release is Feishu support.

• Stop forwarding host provider auth env vars such as OPENAI_API_KEY, OPENAI_BASE_URL, and OLLAMA_API_KEY into codex app-server by default.
• Preserve a manual escape hatch with inheritHostAuthEnv=true for setups that intentionally use env-based auth.
• Improve turn failure messaging so Codex auth conflicts are reported clearly instead of surfacing the raw upstream 401 error.
• Add Feishu support for /codex_start and /codex_stop.
• Add Feishu text-menu interaction so project and thread selection can continue by replying with numbers.
• Fix Feishu private-chat and group-chat binding so selection menus stay interactive until the conversation is bound.

Troubleshooting

If Telegram returns:

Codex authentication failed on this machine. A host OPENAI_API_KEY is overriding Codex login. Clear that env var or set inheritHostAuthEnv=true only if you intentionally want env-based auth.

check these items in order:

1. Confirm Codex is logged in on the machine:

   codex login

2. Remove the conflicting host auth environment variables:

   launchctl unsetenv OPENAI_API_KEY
   launchctl unsetenv OPENAI_BASE_URL
   launchctl unsetenv OPENAI_API_BASE

3. Restart OpenClaw so the plugin process picks up the cleaned environment, then bind the conversation again.

Release

Publish a new npm version with:

npm version patch
npm publish --access public