My First Codex Plugin Experiment: Integrating WeChat and Why It Fell Short

Codex v0.117.0 Plugin system

Codex v0.117.0 introduces a Plugin system that can be accessed from the TUI with the /plugins command. The system defines a three‑level marketplace:

Official repository (currently closed).

Project‑level configuration at $REPO_ROOT/.agents/plugins/marketplace.json.

User‑level configuration at ~/.agents/plugins/marketplace.json.

When the official marketplace is unavailable, community plugins must be installed from a local path, which requires manual cloning and editing of the marketplace JSON file.

WeChat integration steps for Codex

Package a Codex Plugin – Wrap the WeChat integration as a standard Codex Plugin containing two skills: weixin-configure (QR‑code login). weixin-access (pairing code and whitelist management).

These skills reuse the implementation from the Claude Code version.

Implement a standalone bridge – Create server-codex.ts that continuously polls WeChat, injects each message as a turn into the Codex App Server, receives the AI response, and forwards it back to WeChat. The bridge runs in its own terminal process.

Startup script – start-codex.sh launches both the Codex App Server and the WeChat bridge.

The end‑to‑end flow works: a WeChat message is received, processed by the Codex model, and the reply is sent back to WeChat.

Unresolved core issues

1. Conversation not displayed in the Codex TUI. The bridge logs incoming ( ←) and outgoing ( →) messages in its terminal, but the Codex TUI does not render these turns. An OpenAI collaborator responded to Issue #15320 with: “This use case isn’t currently supported, but it’s something we’d like to get to eventually.” No timeline was provided.

2. No push‑notification mechanism. Claude Code provides a private extension notifications/claude/channel that allows the MCP Server to push messages into an active session. Codex plugins operate only in a request‑response mode and cannot proactively inject messages. Issue #15299 lists three possible solutions that remain open:

Convert MCP Server notifications into a Codex CLI thread item.

Expose a local IPC endpoint for active sessions.

Add an extension point similar to Claude Code’s channel.

Community plugin installation workflow

Clone the plugin repository locally, e.g. git clone https://github.com/qufei1993/cc-weixin.

Edit ~/.agents/plugins/marketplace.json and add an entry with the local path prefixed by ./ (absolute paths cause errors).

In the Codex TUI, search for the plugin and install it.

This manual process defeats the intended one‑click installation experience.

Conclusion

The integration functions as a proof‑of‑concept but is marked as experimental support. The dialogue is invisible in the Codex TUI and there is no push‑notification capability, resulting in a noticeably poorer experience compared to the Claude Code version. Resolution of Issues #15299 and #15320 is required for a usable daily‑use solution.