Claude Code
Install Venom Full, authorize your organization, and check the connection from Claude Code.
Venom comes as two plugins from the same marketplace. The venom plugin bundles Venom’s MCP connection and a venom skill that tells Claude when to read and update Venom projects and tasks. Venom Full (venom-full) adds hooks to it: your projects and mentions at the start of a session, guidance around compaction and subagents, and a check after commits, pull requests, and deploys. The Venom server adds its instructions when Claude connects. Your organization’s own practices live in shared skills.
Install.
Use a current Claude Code release. Run both in a Claude Code session to install Venom Full:
/plugin marketplace add venomlabs-dev/plugin
/plugin install venom-full@venomClaude Code installs venom with it. Venom Full uses the venom plugin’s connection, so there’s one sign-in and one set of Venom tools.
Start a new session. Sign in when prompted and select your organization. Your client’s approval settings still apply.
In Claude chat and Cowork, add the venom plugin from the plugin directory on claude.ai and connect Venom on the plugin’s Connectors tab. Venom Full’s hooks are for Claude Code and Codex; it isn’t listed in the plugin directories.
Check the connection.
Ask your agent:
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.
Update or remove.
Manage both plugins with Claude Code’s /plugin command. Removing venom also removes its bundled MCP configuration, and Venom Full’s hooks then do nothing; continued access needs a separate MCP connection.
For Codex and other host packages, see the plugin README.