Codex plugin 0.1.0

First release of the multi-llm Codex plugin: the multi-llm workflow (plan reviews, task generation, implementation and code review fanned out across several LLM CLIs) inside a Codex session, through a multi_llm tool served by a small stdio MCP server bundled with the plugin, and a multi-llm:multi-llm skill that points the model at it.

Install

codex --version                     # 0.159.2 or newer
python3 --version && uv --version   # python3 3.9 or newer, under these exact names
codex plugin marketplace add beastlabai/multi-llm-plugin --ref release \
  --sparse .agents --sparse packaging/codex
codex plugin add multi-llm@beastlabai
# then start a NEW session

Then, once per repository: "Use the multi-llm:multi-llm skill with exactly these arguments: --init". See packaging/codex/README.md for provider keys, upgrades, uninstall and the silent-failure checklist.

What was checked before this release

• Container gate (make codex-package-check, zero quota, --network none rows), all green on the published bytes (plugin digest 9041d389…):
  • codex 0.159.2 (the declared minimum): 10/10 rows
  • codex 0.163.0 (the pinned container codex): 17/17 rows
  • codex 0.164.0 (npm's newest on release day): 10/10 rows; codex features list as recorded (plugins stable/true, plugin_hooks removed/false, multi_agent stable/true)
  • rows include an offline Git-marketplace install pinned with --ref release and both --sparse paths, the installed tree compared blob for blob with the ref, the skill advertised, the tool listed and called, and a promoted release reaching the install through marketplace upgrade + plugin add.
  • upstream's validate_plugin.py ships in no codex since 0.156.1: recorded as absent; the compatibility layout is held to restated packaging-guide rules and to codex's own ingestion.
• As a user would: the install pinned to this tag on a fresh container that never saw the repository (stock node:22-bookworm-slim, codex 0.164.0 from npm, uv from the official installer), all six release criteria passing. The record is committed as skills/multi-llm/tests/container/records/20261023T132656Z-codex-release-network-check.json. After promotion, the published --ref release line was run the same way in a second fresh container: it resolved to the tagged commit, all six criteria passed, and marketplace upgrade + plugin add left the install unchanged.

Platforms

Linux is the only verified platform. macOS is unmeasured (the run's login shell reads ~/.bash_profile/~/.profile, not ~/.zprofile). Windows is unsupported for the tool route; use the file route (install-host codex).

Upgrading later

codex plugin marketplace upgrade beastlabai, then codex plugin add multi-llm@beastlabai, then a new session. Re-adding the marketplace with a different --ref is refused by codex; remove it first to switch refs.

No providers.yaml migration is needed (first release).