VenomDocs

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.

LevelWhat the agent gets
Plugin + hooksThe 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 hooksThe 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.
PluginThe 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 hooksThe app can’t load a plugin, but runs Venom’s hooks next to the server and rules file.
MCP onlyThe 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.

AgentLevelInstallHooksChecked
Claude CodePlugin + hooksClaude CodeVenom Full: seen workingSigned in and used every day
CodexPlugin + hooksCodexVenom Full: seen workingSigned in and used every day
AmpPlugin + hooksamp mcp add venom https://mcp.venomlabs.dev/, amp skill add venomlabs-dev/plugin --global, then the Amp pluginAmp plugin: not run yet, needs an Amp accountNot run yet: everything except amp mcp add needs an Amp account. The Amp plugin is typechecked and unit-tested
OpenCodePlugin + some hooksOpenCodeOpenCode plugin: unit-tested; in Kilo, the model received its milestone noteInstall checked, 1.19.5 and 2.3.0
CursorPlugin + some hooksCursorvenom-full/cursor: builtPackage passes Cursor’s plugin checker; Cursor CLI 2026.11.17 loads the server. Not tried in the Cursor app yet
GitHub Copilot CLIPlugin + some hookscopilot plugin marketplace add venomlabs-dev/plugin, then copilot plugin install venom@venomvenom-full/copilot: seen on a test model, Copilot CLI 1.0.114Install checked, 1.0.112
VS Code (Copilot)Plugin + some hooksInstall the plugin with Copilot CLI; VS Code agent mode loads Copilot CLI pluginsvenom-full/copilot: built, not run in VS CodeNot tried in VS Code yet
Gemini CLIPlugin + some hooksGemini CLIvenom-full/gemini: builtInstall checked, 0.68.0
Antigravity CLIPlugin + some hooksgit clone https://github.com/venomlabs-dev/plugin ~/.venom-plugin, then agy plugin install ~/.venom-pluginvenom-full/antigravity: seen working, 1.5.11 (session start and milestone note)Install checked, 1.5.11: skill, rule and server
Grok BuildPlugin + some hooksgrok plugin install venomlabs-dev/plugin --trust. If Venom is already in Claude Code, Grok Build picks it up with no setupvenom-full/grok: seen working, 1.0.89 (milestone note)Install checked, 1.0.89
Qwen CodePlugin + some hooksqwen extensions install venomlabs-dev/plugin, then pick venomvenom-full/qwen: seen on a test model, 0.28.0Install checked, 0.27.4
Factory DroidPlugin + some hooksdroid plugin marketplace add venomlabs-dev/plugin, droid plugin install venom@plugin --scope user, then droid mcp add venom https://mcp.venomlabs.dev --type httpvenom-full/droid: built, needs a Factory account to runPartly, 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
KiroPlugin + some hooksImport platforms/agent-plugin as a Power, or kiro-cli powers install with that folder, and add the steering filevenom-full/kiro: built, needs a Kiro login to runThe Power installs in Kiro CLI 3.4.0; the rest needs a Kiro login
JetBrains JuniePlugin + some hooks/extensions marketplace add venomlabs-dev/plugin, then /extensions install venomvenom-full/junie: builtNot run yet: Junie CLI 26.9.7 didn’t start here
Mistral VibePlugin + some hooksgit 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-invenom-full/vibe: loads in Vibe’s plugin loader, not run with a modelPartly, 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
PiPlugin + some hookspi install git:github.com/venomlabs-dev/plugin, then pi mcp add venom --url https://mcp.venomlabs.devvenom-full/pi: seen on a test model, Pi 1.5.2Install checked, 1.5.2
OpenClawPlugin + some hooksgit clone https://github.com/venomlabs-dev/plugin ~/.venom-plugin, then openclaw plugins install ~/.venom-plugin --accept-capabilitiesvenom-full/openclaw: built; it also carries the server and skillInstall checked, 2026.11.5: the plugin brings the skill and server. Installing from the marketplace or a git: URL fails
Muse CodePlugin + some hooksgit 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 --uservenom-full/muse: builtInstall checked, 1.4.23: skill and server listed. The plugin’s own server entry waits for approval in Muse
Augment (Auggie)Plugin + some hooksauggie install git:github.com/venomlabs-dev/plugin, then auggie mcp add venom -t http -u https://mcp.venomlabs.devvenom-full/auggie: loads in Auggie 1.2.2, not run with a modelInstall checked, 1.2.2
GoosePlugingoose plugin install https://github.com/venomlabs-dev/plugin for the skill, then the server through the extension linkNone: Goose hooks can’t add contextPartly, 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 CoworkPluginvenom from the plugin directory; see MCP setupNone: no hooks in the appNot tried in the app yet
Devin CLIPlugin + some hooksmcp_config.json in .devin/, then devin mcp login venom, and VENOM.md in AGENTS.mdvenom-full/devin: built; hooks file format checked with devin migrate hooksInstall checked, 3000.14. Devin plugins need a Devin login, not tried yet
ClinePlugin + some hookscline 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: builtInstall checked, Cline CLI 3.0.74: server, rule and skill. Not tried in the VS Code extension yet
Hermes AgentPlugin + some hookshermes 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.yamlvenom-full/hermes: built; Hermes’s install scanner passes itPartly, 0.23.2: skill enabled and the server reaches Venom’s sign-in. Hermes refuses the plugin itself
Kilo CodePlugin + some hookskilo.json merged into kilo.jsonc, with VENOM.md in instructionsOpenCode plugin: seen working, Kilo 7.8.27 (milestone note)Install checked, Kilo CLI 7.8.27
Windsurf and Devin Desktop (Cascade)Plugin + some hooksmcp_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
ZedMCP onlycontext_servers in settings, with url, and VENOM.md in AGENTS.mdNone: no hooksNot tried in the app yet
WarpMCP onlySettings → MCP Servers, and VENOM.md in AGENTS.mdNone: no hooksNot tried in the app yet
CrushMCP + some hookscrush.json, an http server with "oauth": true, and VENOM.md in AGENTS.mdvenom-full/crush: seen on a test model, 0.101.0; no end-of-turn questionCrush 0.101.0 reaches the server; its sign-in prompt is not confirmed
ContinueMCP onlyA streamable-http server under mcpServers in config.yaml, and VENOM.md in .continue/rules/None: no hooksContinue CLI 1.5.47 reaches the server
Kimi CodePlugin + some hooksVenom’s Kimi plugin, with the server, skill and hooks: clone venomlabs-dev/venom-full, then /plugins install <clone>/kimivenom-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 AssistantMCP onlySettings → Tools → AI Assistant → MCP, and VENOM.md in the project rulesNone: no hooksNot tried in the app yet
Grok BotMCP onlyA 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 liveNone: no hooksNot tried in the app yet
Trae and other MCP clientsMCP onlyA remote Streamable HTTP server at https://mcp.venomlabs.dev/, and VENOM.md in the app’s rules fileNoneNot 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:

AgentSign in
Claude Code/mcp, then authenticate venom
Codexcodex mcp login venom
CursorCursor Settings → MCP, then connect venom
Gemini CLI/mcp auth venom
OpenCodeopencode mcp auth venom
GitHub Copilot CLI/mcp
Antigravity CLI/plugin, then sign in to venom
Grok Build/mcps, select venom, then press i
Devin CLIdevin mcp login venom
Other agentsThe 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.

Venom

Venom AI by Venom Labs. Built by humans. Logged by agents.

On this page