codex2opencode is a release-ready local bridge that lets Codex hand work to Opencode without turning the repo into a multi-agent framework.

It keeps the boundary intentionally simple: thin skill on the Codex side, session/state/locking/export verification inside the bridge, and a stable CLI you can install from PyPI today.

Initial public release of codex2opencode, a standalone local one-way bridge from Codex to Opencode.

Highlights:

• Adds the codex2opencode CLI with ask, status, forget, gc, and doctor
• Persists Opencode sessions via native sessionID with deterministic per-thread locking
• Keeps the Codex-facing codex-to-opencode skill thin while the bridge owns session state, locking, export verification, and error translation
• Supports Opencode-native session controls including --new, --fork, and --title
• Includes natural-language trigger guidance for short forms such as 问问oc, 给oc看看, and 让oc review一下
• Ships complete day-one docs: README.md, CONTRIBUTING.md, AGENTS.md, ARCHITECTURE.md, and DEVELOPMENT.md
• Publishes with GitHub Actions and PyPI Trusted Publishing

Verified before release:

• PYTHONPATH=bridge python3 -m unittest discover -s tests -p 'test_*.py' -v
• PYTHONPATH=bridge CODEX2OPENCODE_RUN_REAL=1 python3 -m unittest tests.test_real_opencode_cli -v
• Direct codex2opencode ask --prompt "Reply with ok only" --workspace "$PWD" --new smoke
• Direct codex2opencode doctor --workspace "$PWD" smoke
• .venv-release/bin/python -m build
• .venv-release/bin/python -m twine check dist/*
• GitHub Actions test and release workflows green
• PyPI publication confirmed: https://pypi.org/project/codex2opencode/

Notes:

• This repository intentionally stays narrow: Codex -> Opencode only
• Already-open Codex sessions may need a restart to pick up newly installed or updated skills
• This release follows the same single-responsibility bridge boundary validated in codex2claude