Venom docs
Documentation for Venom, the operating layer for human and AI teams: the workspace apps, the venom CLI and harness, the orchestrator and Venom Cloud, for people and agents.
New here? Start with Getting started. Agents: /docs/llms.txt lists every page.
Venom is the operating layer for human and AI teams. It runs in Venom Cloud, in your cloud or on your servers, with policy, memory, routing, budgets and audit under every app. Choose how to run it.
Products
- Venom Notes
- Venom Tasks
- Venom Chat
- Venom Calendar
- Venom People
- Venom Funnel
- Venom Outreach
- Venom Support
- Venom Forms
- Venom Incidents
- Venom Status
- Venom Comms
- Venom Line
- Venom Flags
- Venom Experiments
- Venom Computers
- Venom Agents
- Venom Studio
- Venom Cloud
- Venom mesh and router
- Venom daemon
- venom CLI
- Editor and browser clients
All sections
Getting started
Pick where to start with venom, whether you use the CLI, run your own models, use Venom Cloud or build an app on the harness.
Products
Every Venom product in one page, what each is for, its MCP endpoint and whether it is an add-on, from the workspace apps to the CLI, the orchestrator, the desktop daemon and the editor clients.
Build with Venom
Build on every Venom product from code or an agent. Each product has MCP tools and REST routes behind the same API keys and OAuth scopes, with webhooks for what changed. Start here for auth, conventions, a quick start and a page per product.
The venom CLI
How the venom command is organised, the ways to run it (terminal UI, print mode, JSON, RPC) and where each part of it is documented.
Configuration
Where venom reads its settings from, which file or variable wins, and how to see, check and change the configuration in force.
The harness library
What @venom/harness is, which package to use for your app, how to install it and where each part of the library is documented.
Server API (venom serve)
Run venom's agent sessions behind HTTP and Server-Sent Events with venom serve, so an app in any language can create sessions, send prompts, stream events and answer approvals.
Orchestrator
Run venom's self-hosted OpenAI-compatible gateway in front of your own inference servers and cloud providers, and call it from any OpenAI SDK.
Voice
Speak to venom and have it speak back, through your own speech models or cloud ones, behind one OpenAI-shaped audio API.
Security
How venom decides what the agent may do, keeps secrets out of the model, contains commands in an OS sandbox and leaves evidence you can verify offline.
Automation
Run venom without sitting at the keyboard, from scripted multi-agent pipelines and plan-then-execute runs to scheduled agents, background goals and pull request review bots.
Plugins and extensions
Extend venom with plugins, pi packages, Claude Code plugins, hooks, sounds, skills, MCP servers, themes, templates and roles.
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.
Venom Cloud
What Venom Cloud is, how its console is laid out, which role opens which page, and where the console and API guides start.
Venom Notes
What Venom Notes is, where it lives, who can open it, and how its screen is laid out.
Venom Incidents
Error tracking for your own apps in your own Venom Cloud: errors grouped by cause with the release and the flags served, triaged from the keyboard or by an agent.
Venom Comms
One API for SMS, WhatsApp, RCS, Telegram and phone calls, through your own provider account, with opt-outs, quiet hours, fallback and spend in one place.
Venom Funnel guides
Guides for the parts of Venom Funnel that go beyond the pipeline board, starting with Outreach, personalised follow-up sequences.
Venom Calendar
One availability across every calendar you own, and booking pages that respect it: several Google accounts, .ics feeds, buffers, notice and limits, with bookings that update People, Funnel and Outreach.
Venom Computers
A persistent browser for every agent, running on your own daemons, with logins that stay and a person who can take over for a 2FA code or a CAPTCHA.
Venom Agents
Chats with coding agents on your own repositories and with agents on your computers, run on your own daemons and reached from the cloud.
Venom Studio
Make slide decks, pages and HTML pages from blocks and charts, change one slide or block at a time, keep every version, and share by link, from the console or from an agent.
Mesh
How Venom Cloud sends requests to GPUs you own (your key groups' daemons) or to public nodes run by anyone, while provider keys and the data path stay on those machines.
Deploy
Run venom's orchestrator and console on your own hardware, from one laptop to a Kubernetes cluster or an air-gapped site, and build and verify releases.
Evals
Measure how venom does on real coding tasks, gate harness changes with a paired comparison, keep eval spend capped, and turn your own sessions into a local fine-tuning dataset.
Reference
Lookup tables for venom as a whole, covering environment variables, ports, error codes, x-venom headers, limits, a glossary, make targets and the design records.
Cookbook
End-to-end recipes that put venom's pieces together, from an offline coding setup to a multi-tenant SaaS with a phone agent.
API reference
The HTTP APIs of venom serve, the orchestrator and Venom Cloud, generated from their contracts.