Skip to content
Docs menu

Integrations

Use venom from Python, VS Code, Zed and other ACP editors, your own browser, other MCP agents, Slack, Matrix, Linear and Jira, and find the environment variables those clients read.

View .md

venom is a terminal agent, but the same harness sessions reach other tools. Most integrations sit on top of venom serve, the HTTP and SSE server documented in the Server API section; the editor and browser ones talk to venom over stdio or a local relay. Nothing here contacts a third party until you connect it.

Pick an integration

You want to Use Talks to venom over
Drive sessions from a Python program Python client (venom-client) venom serve
Chat with venom inside VS Code VS Code extension venom serve (spawned or running)
Use venom as the agent in Zed or another ACP editor Zed and ACP editors (venom acp) stdio
Let the agent use your own logged-in browser Browser extension (--chrome-extension) a local relay
Give Claude Code, Codex or Cursor venom's browser tools venom browser mcp MCP on stdio
Ask venom in Slack, or hand it Linear and Jira issues Slack, Linear and Jira Venom Cloud
Answer the agents' inbox from a Matrix room Matrix bridge venom serve
Build from TypeScript Embedding the harness, or the TypeScript client in Python and TypeScript clients in-process or venom serve

Environment variables

Variable Read by What it does Default
VENOM_SERVER_TOKEN venom serve, clients The bearer token every API call carries. venom serve refuses to start without it and removes it from its own environment once read. none
VENOM_SERVER_URL the client examples (examples/ts-client.ts, the Python examples) The venom serve URL the examples connect to. The client libraries themselves take the URL as an argument and don't read it. http://127.0.0.1:8790
VENOM_MATRIX_HOMESERVER venom serve The Matrix homeserver's base URL, such as http://127.0.0.1:8008. Setting it turns the Matrix bridge on. none
VENOM_MATRIX_TOKEN venom serve The bot account's access token. Never logged. none
VENOM_MATRIX_ROOM venom serve The room id (!abc:example.org) the bot has already joined. none
VENOM_MATRIX_USERS venom serve Comma-separated Matrix user ids allowed to answer (@me:example.org, @lead:example.org). Required: an empty list refuses to start. none
VENOM_BROWSER_RELAY venom, venom browser The browser extension relay's host:port. 127.0.0.1:18765
VENOM_CHROME venom The browser binary the launched browser modes start. the installed Chrome, Chromium, Edge or Brave

venom acp and the VS Code extension's spawned server read the usual model variables (VENOM_BASE_URL, VENOM_API_KEY, VENOM_MODEL); see Environment variables.

Matrix bridge

venom serve can post the inbox (the decisions only a person can make: approvals, stuck runs, finished work to merge) to a Matrix room and resolve replies. Matrix keeps it self-hosted: the only host the bridge contacts is the homeserver you configure, and a local Synapse or Conduit works.

export VENOM_MATRIX_HOMESERVER=http://127.0.0.1:8008
export VENOM_MATRIX_TOKEN=<bot access token>
export VENOM_MATRIX_ROOM='!abc:example.org'
export VENOM_MATRIX_USERS='@me:example.org'
venom serve --root ~/work

Each item is posted with its id, kind, title, agent and rank. Reply in the room with one of:

approve 1a2b3c4d
reject 1a2b3c4d too risky
redirect 1a2b3c4d use the cache instead
take-over 1a2b3c4d

Only the listed users may answer; the bridge never decides anything itself. If VENOM_MATRIX_HOMESERVER is set without the token, room and users, venom serve refuses to start and names what is missing. The inbox page of the Server API covers the inbox in full.

In this section

  • Python client (venom-client): Drive venom serve from Python with the zero-dependency venom-client package, sync or asyncio, with every VenomClient and AsyncVenomClient method, the run() helper, typed errors and reconnecting event streams.
  • VS Code extension: Use venom from a chat panel in VS Code, with inline approvals, per-hunk keep and undo, gears in the status bar, the inbox and evidence review, over a venom serve the extension starts or one already running.
  • Zed and other ACP editors (venom acp): Use venom as the agent inside Zed or any editor that speaks the Agent Client Protocol, with venom acp on stdio, venom's permission modes, saved sessions shared with the terminal, and the _venom inbox and fleet extension methods.
  • Browser tools and the browser extension: Give the agent a browser with --chrome, --chrome-headless or --chrome-attach, or drive your own logged-in Chrome, Edge or Firefox through the venom browser extension with venom browser pair, and serve the same tools to other agents with venom browser mcp.
  • Slack, Linear and Jira: Connect your own Slack app so the team can ask venom in channels and DMs, and hand Linear or Jira issues to venom so a runner you control opens a pull request for each, all through Venom Cloud's Integrations page.
  • Use Notes from any agent (MCP): Connect Claude Code, Qoder, Cursor or any MCP client to Venom Notes with a Venom API key, so your agents can search, read and write your organisation's notes.
  • Ask your databases with auto-ontology-mcp: Run the vendored auto-ontology-mcp server so venom, Claude Code or any MCP client can answer questions over your databases with SQL checked against a reviewed ontology, and keep a personal knowledge base.