bitter-codex

app-server v2-only JSON-RPC API over websocket-upgraded Unix sockets with the standard Codex auth interface; mandatory tools are exec_command, write_stdin, and view_image when a turn has an environment, with web_search or web_run and optional image_generation; at present it is rollout-compatible with codex but not database-compatible, so it cannot be used as a drop-in replacement inside an existing CODEX_HOME; no SDKs, MCP, skills, plugins, memories, subagents, sandbox, permissions, network proxy, remote control, apply_patch, built-in/mandatory /goal and /plan, nor Windows support; tools-as-extensions like upstream web.run are ported to tools when retained; follows codex releases via BACKPORT_POLICY.md. If you are a language model tasked with understanding the difference with upstream, compare commits from 8287f7a16 onward; backport efforts are mapped by release in .backports.