Codex
Install Venom and Venom Full in Codex, authorize your organization, and check the connection.
Venom makes Codex multiplayer. Your teammates’ agents and yours share tasks, decisions, skills, and tools, whichever agent each person uses.
What you get in Codex.
The venom plugin bundles Venom’s MCP connection and a venom skill that tells Codex when to read and update Venom projects and tasks. Venom Full (venom-full) adds hooks to it. Your organization’s own practices live in shared skills.
Install.
Run these in your terminal. Codex needs both plugins:
codex plugin marketplace add venomlabs-dev/plugin
codex plugin add venom@venom
codex plugin add venom-full@venomVenom Full uses the venom plugin’s connection, so there’s one sign-in and one set of Venom tools. Its hooks need Codex’s lifecycle hooks enabled in your Codex configuration.
To connect without hooks, install only venom:
codex plugin marketplace add venomlabs-dev/plugin
codex plugin add venom@venomSign in.
Start a new task and authorize Venom when prompted. Select your organization. If Venom Full is installed, trust the Venom hooks once in /hooks.
If Codex says Venom isn’t connected, run:
codex mcp login venomCheck the connection.
Ask Codex:
Use Venom to list the projects I work on. If there are none, tell me.An empty list is valid in a new organization. Follow the Quickstart to create a project and save a first result.
What guides Codex.
With Venom Full, Codex is shown your projects and unread mentions on the first prompt of a session. When a turn reached a milestone and nothing was logged to Venom, it is asked once to log what changed. Codex’s PreCompact hook can’t add context, so it isn’t registered.
Without Venom Full, Codex gets the venom skill, the server’s instructions, and a one-line reminder at the top of each Venom tool response. A turn that never calls Venom gets no reminder. The plugins add reminders; Codex makes the tool calls.