Agents
All agents.
What Venom gives each coding agent, how to install it, and what we checked in each app.
Every agent connects to the same Venom MCP server, https://mcp.venomlabs.dev/, with OAuth and no API key, through a Venom plugin or extension wherever the agent supports one.
Venom needs its plugin.
The MCP server alone gives an agent Venom’s tools; the plugin tells it when to use them: read the project and task before acting, log what changed. Without the plugin, agents rarely use Venom. Add the MCP server by itself only in an app that can’t load a plugin, and add Venom’s rules file there.
Setup files and packages live in the venomlabs-dev/plugin repository. The code-based plugins, for OpenCode and Amp, and the hooks live in venomlabs-dev/venom-full.
Support levels.
| Level | What the agent gets |
|---|---|
| Plugin + hooks | The Venom plugin, plus hooks that show your projects and new mentions at the start of a session and remind the agent to log after commits, pull requests and deploys. The best experience. |
| Plugin + some hooks | The Venom plugin, plus a hooks package that adds Venom’s guidance at the start of a session and reminds the agent to log after commits, pull requests, merges, releases and deploys, with one question at the end of a turn where the app allows it. It doesn’t show your projects and mentions yet. |
| Plugin | The Venom server and its instructions (a skill, rule or context file). Nothing reminds the agent during the session, so it relies on those instructions. |
| MCP + some hooks | The app can’t load a plugin, but runs Venom’s hooks next to the server and rules file. |
| MCP only | The app can’t load a Venom package. Add the server and Venom’s rules file yourself. |
Compatibility.
“Install checked” means we installed the app in a clean environment, installed Venom with the command shown, and the app’s own listing showed Venom’s server and its skill, rule or context file. Signing in to Venom needs a person in a browser, so that step was checked only where the row says so. In the Hooks column, “seen working” means the app’s model received the hook’s text in a real session; “seen on a test model” means the same, with a local stand-in model because the app needed an account; “built” means the package follows the app’s documentation and passes our tests but hasn’t run in the app yet.
| Agent | Level | Install | Hooks | Checked |
|---|---|---|---|---|
| Claude Code | Plugin + hooks | Claude Code | Venom Full: seen working | Signed in and used every day |
| Codex | Plugin + hooks | Codex | Venom Full: seen working | Signed in and used every day |
| Amp | Plugin + hooks | amp mcp add venom https://mcp.venomlabs.dev/, amp skill add venomlabs-dev/plugin --global, then the Amp plugin | Amp plugin: not run yet, needs an Amp account | Not run yet: everything except amp mcp add needs an Amp account. The Amp plugin is typechecked and unit-tested |
| OpenCode | Plugin + some hooks | OpenCode | OpenCode plugin: unit-tested; in Kilo, the model received its milestone note | Install checked, 1.19.5 and 2.3.0 |
| Cursor | Plugin + some hooks | Cursor | venom-full/cursor: built | Package passes Cursor’s plugin checker; Cursor CLI 2026.11.17 loads the server. Not tried in the Cursor app yet |
| GitHub Copilot CLI | Plugin + some hooks | copilot plugin marketplace add venomlabs-dev/plugin, then copilot plugin install venom@venom | venom-full/copilot: seen on a test model, Copilot CLI 1.0.114 | Install checked, 1.0.112 |
| VS Code (Copilot) | Plugin + some hooks | Install the plugin with Copilot CLI; VS Code agent mode loads Copilot CLI plugins | venom-full/copilot: built, not run in VS Code | Not tried in VS Code yet |
| Gemini CLI | Plugin + some hooks | Gemini CLI | venom-full/gemini: built | Install checked, 0.68.0 |
| Antigravity CLI | Plugin + some hooks | git clone https://github.com/venomlabs-dev/plugin ~/.venom-plugin, then agy plugin install ~/.venom-plugin | venom-full/antigravity: seen working, 1.5.11 (session start and milestone note) | Install checked, 1.5.11: skill, rule and server |
| Grok Build | Plugin + some hooks | grok plugin install venomlabs-dev/plugin --trust. If Venom is already in Claude Code, Grok Build picks it up with no setup | venom-full/grok: seen working, 1.0.89 (milestone note) | Install checked, 1.0.89 |
| Qwen Code | Plugin + some hooks | qwen extensions install venomlabs-dev/plugin, then pick venom | venom-full/qwen: seen on a test model, 0.28.0 | Install checked, 0.27.4 |
| Factory Droid | Plugin + some hooks | droid plugin marketplace add venomlabs-dev/plugin, droid plugin install venom@plugin --scope user, then droid mcp add venom https://mcp.venomlabs.dev --type http | venom-full/droid: built, needs a Factory account to run | Partly, 1.14.0: the server added with droid mcp add is listed; the plugin’s skill and rules install but Droid’s listing doesn’t show them, and Droid rejects the plugin’s own server entry |
| Kiro | Plugin + some hooks | Import platforms/agent-plugin as a Power, or kiro-cli powers install with that folder, and add the steering file | venom-full/kiro: built, needs a Kiro login to run | The Power installs in Kiro CLI 3.4.0; the rest needs a Kiro login |
| JetBrains Junie | Plugin + some hooks | /extensions marketplace add venomlabs-dev/plugin, then /extensions install venom | venom-full/junie: built | Not run yet: Junie CLI 26.9.7 didn’t start here |
| Mistral Vibe | Plugin + some hooks | git clone https://github.com/venomlabs-dev/plugin ~/.vibe/plugins/venom, then vibe mcp add venom --url https://mcp.venomlabs.dev --transport streamable-http, which starts Venom’s sign-in | venom-full/vibe: loads in Vibe’s plugin loader, not run with a model | Partly, 3.1.3: Vibe’s plugin loader reads the skill and the server is in its config; Vibe has no listing command to confirm more |
| Pi | Plugin + some hooks | pi install git:github.com/venomlabs-dev/plugin, then pi mcp add venom --url https://mcp.venomlabs.dev | venom-full/pi: seen on a test model, Pi 1.5.2 | Install checked, 1.5.2 |
| OpenClaw | Plugin + some hooks | git clone https://github.com/venomlabs-dev/plugin ~/.venom-plugin, then openclaw plugins install ~/.venom-plugin --accept-capabilities | venom-full/openclaw: built; it also carries the server and skill | Install checked, 2026.11.5: the plugin brings the skill and server. Installing from the marketplace or a git: URL fails |
| Muse Code | Plugin + some hooks | git clone https://github.com/venomlabs-dev/plugin ~/.venom-plugin, muse plugins install ~/.venom-plugin/platforms/agent-plugin, then muse mcp add venom --url https://mcp.venomlabs.dev --user | venom-full/muse: built | Install checked, 1.4.23: skill and server listed. The plugin’s own server entry waits for approval in Muse |
| Augment (Auggie) | Plugin + some hooks | auggie install git:github.com/venomlabs-dev/plugin, then auggie mcp add venom -t http -u https://mcp.venomlabs.dev | venom-full/auggie: loads in Auggie 1.2.2, not run with a model | Install checked, 1.2.2 |
| Goose | Plugin | goose plugin install https://github.com/venomlabs-dev/plugin for the skill, then the server through the extension link | None: Goose hooks can’t add context | Partly, 1.60.1: skill listed; the server was added by hand in config.yaml and is listed, the link itself wasn’t tried |
| Claude chat and Cowork | Plugin | venom from the plugin directory; see MCP setup | None: no hooks in the app | Not tried in the app yet |
| Devin CLI | Plugin + some hooks | mcp_config.json in .devin/, then devin mcp login venom, and VENOM.md in AGENTS.md | venom-full/devin: built; hooks file format checked with devin migrate hooks | Install checked, 3000.14. Devin plugins need a Devin login, not tried yet |
| Cline | Plugin + some hooks | cline mcp add venom --transport streamable-http --yes https://mcp.venomlabs.dev, cline skill add venomlabs-dev/plugin --skill venom -y, and the rules file in .clinerules/ | venom-full/cline: built | Install checked, Cline CLI 3.0.74: server, rule and skill. Not tried in the VS Code extension yet |
| Hermes Agent | Plugin + some hooks | hermes skills install https://raw.githubusercontent.com/venomlabs-dev/plugin/main/skills/venom/SKILL.md, then add venom with url: https://mcp.venomlabs.dev and auth: oauth under mcp_servers in ~/.hermes/config.yaml | venom-full/hermes: built; Hermes’s install scanner passes it | Partly, 0.23.2: skill enabled and the server reaches Venom’s sign-in. Hermes refuses the plugin itself |
| Kilo Code | Plugin + some hooks | kilo.json merged into kilo.jsonc, with VENOM.md in instructions | OpenCode plugin: seen working, Kilo 7.8.27 (milestone note) | Install checked, Kilo CLI 7.8.27 |
| Windsurf and Devin Desktop (Cascade) | Plugin + some hooks | mcp_config.json with serverUrl, and the rules file in .windsurf/rules/ | venom-full/devin: built (same harness as Devin CLI) | Not tried in the app yet |
| Zed | MCP only | context_servers in settings, with url, and VENOM.md in AGENTS.md | None: no hooks | Not tried in the app yet |
| Warp | MCP only | Settings → MCP Servers, and VENOM.md in AGENTS.md | None: no hooks | Not tried in the app yet |
| Crush | MCP + some hooks | crush.json, an http server with "oauth": true, and VENOM.md in AGENTS.md | venom-full/crush: seen on a test model, 0.101.0; no end-of-turn question | Crush 0.101.0 reaches the server; its sign-in prompt is not confirmed |
| Continue | MCP only | A streamable-http server under mcpServers in config.yaml, and VENOM.md in .continue/rules/ | None: no hooks | Continue CLI 1.5.47 reaches the server |
| Kimi Code | Plugin + some hooks | Venom’s Kimi plugin, with the server, skill and hooks: clone venomlabs-dev/venom-full, then /plugins install <clone>/kimi | venom-full/kimi: seen on a test model, 2.6.3 (session start) | Not run yet: Kimi Code 2.6.3 needs a Kimi login |
| JetBrains AI Assistant | MCP only | Settings → Tools → AI Assistant → MCP, and VENOM.md in the project rules | None: no hooks | Not tried in the app yet |
| Grok Bot | MCP only | A custom remote connector in Connect apps. Grok Bot installs plugins from the Cursor Marketplace, so it gets the Venom plugin once the Cursor listing is live | None: no hooks | Not tried in the app yet |
| Trae and other MCP clients | MCP only | A remote Streamable HTTP server at https://mcp.venomlabs.dev/, and VENOM.md in the app’s rules file | None | Not tried |
In Claude Code and Codex, the hooks come from Venom Full (venom-full). Every other agent gets its own hooks package from a folder of venomlabs-dev/venom-full, linked in the Hooks column, with install steps in its README. Install it next to venom; don’t install the venom-full plugin itself outside Claude Code and Codex, because other apps skip or reject its hooks.
T3 Code runs Claude Code, Codex, OpenCode, and Cursor with their own configuration, so set up Venom for those and T3 Code uses it.
Sign in.
Each agent opens Venom’s sign-in the first time it connects, or when you ask it to:
| Agent | Sign in |
|---|---|
| Claude Code | /mcp, then authenticate venom |
| Codex | codex mcp login venom |
| Cursor | Cursor Settings → MCP, then connect venom |
| Gemini CLI | /mcp auth venom |
| OpenCode | opencode mcp auth venom |
| GitHub Copilot CLI | /mcp |
| Antigravity CLI | /plugin, then sign in to venom |
| Grok Build | /mcps, select venom, then press i |
| Devin CLI | devin mcp login venom |
| Other agents | The app’s MCP settings |
Pick your organization when Venom asks. See Authorize for what the connection can do.
What was tested.
The table above comes from checks on 16 and 18 November 2026; the hooks packages were built and checked on 18 November. The sign-in steps follow each app’s documentation; we didn’t sign in during these checks except where a row says so. The plugin repository’s coverage notes have the details for each app, including what didn’t install and why.