# Venom > Venom is the operating layer for human and AI teams: a workspace of apps (notes, tasks, people, support, chat, forms, flags, experiments, incidents, comms) with agents as members, the venom coding agent and its harness library, and a self-hosted OpenAI-compatible orchestrator under them. It runs in Venom Cloud, in your cloud or on your servers. Every page is also served as markdown: add `.md` to its URL. All pages in one file: https://cloud.usevenom.dev/docs/llms-full.txt. Search index: https://cloud.usevenom.dev/docs/search.json. ## Getting started - [Getting started](https://cloud.usevenom.dev/docs/getting-started.md): 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. - [Choose how to run Venom](https://cloud.usevenom.dev/docs/getting-started/choose-how-to-run.md): Compare Venom Cloud, your own cloud and your own servers or an air-gapped site, where the data lives in each, what can leave, and where the install guides are. - [venom CLI quickstart](https://cloud.usevenom.dev/docs/getting-started/cli-quickstart.md): Install the venom CLI, point it at a model, run a first session and check the setup with venom doctor. - [Venom Cloud quickstart](https://cloud.usevenom.dev/docs/getting-started/cloud-quickstart.md): Sign up, create an API key, install the venom CLI, point it at Venom Cloud and test it. - [Install venom](https://cloud.usevenom.dev/docs/getting-started/install.md): Install, update and remove the venom CLI on macOS, Linux and Windows, from the release installer, by hand, or from source. - [Local or cloud models](https://cloud.usevenom.dev/docs/getting-started/local-or-cloud.md): Choose where venom's model runs (Ollama on this machine, the desktop daemon, your own orchestrator, Venom Cloud or any OpenAI-compatible provider) and point the CLI at it. - [Your first gear](https://cloud.usevenom.dev/docs/getting-started/first-gear.md): Switch between cheap, normal, strong and local models in one keystroke with gears, build a gear for your budget with the gear wizard, and make it the default. - [Troubleshooting](https://cloud.usevenom.dev/docs/getting-started/troubleshooting.md): Diagnose a venom setup with venom doctor and fix the common install, endpoint, key, model, sandbox and trust problems. ## Products - [Products](https://cloud.usevenom.dev/docs/products.md): 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 with Venom](https://cloud.usevenom.dev/docs/developers.md): 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. - [Authentication and scopes](https://cloud.usevenom.dev/docs/developers/auth.md): Which credential to use for each Venom API. Personal and team API keys, OAuth 2.1 for MCP clients with its endpoints and token lifetimes, the scopes per product, service agents, and the keys that belong to app runtimes. - [The REST twin and OpenAPI](https://cloud.usevenom.dev/docs/developers/rest.md): Call Venom's workspace products over plain HTTP at /api/v1. Each route runs the MCP tool of the same name, with the same keys, checks and limits, an OpenAPI 3.1 document, If-Match for safe writes and Idempotency-Key for retries. - [MCP servers](https://cloud.usevenom.dev/docs/developers/mcp.md): Connect an agent to Venom over MCP. One connection at /workspace/mcp whose listed products you switch on, or one server per product at /workspace/mcp/, the connect commands for common clients, and how a raw JSON-RPC call looks. - [Errors, limits, idempotency and pagination](https://cloud.usevenom.dev/docs/developers/conventions.md): How the workspace APIs answer errors, how many requests they take a minute, how to retry a create without making it twice, how to write only when nothing changed since your read, and how to page through lists. - [Webhooks and events](https://cloud.usevenom.dev/docs/developers/webhooks.md): Get told when something happens in Venom. Add an org webhook endpoint, pick its events, verify the signature, handle retries, and see every event type each product sends. - [Build on Venom Notes](https://cloud.usevenom.dev/docs/developers/globe.md): Read, write and search notes and databases from code or an agent. Write meeting notes, file suggestions for a person to review, query databases and follow org vault changes over REST or MCP. - [Build on Venom Tasks](https://cloud.usevenom.dev/docs/developers/tasks.md): Create, find and update Tasks issues from code, and run agents that claim delegated work, report progress and hand it back, over REST or MCP. - [Build on Venom People](https://cloud.usevenom.dev/docs/developers/people.md): Search, add and update the people a member knows, log interactions and draft follow-ups from code or an agent, over REST or MCP. People is personal, so every call acts for one member. - [Build on Venom Funnel and Outreach](https://cloud.usevenom.dev/docs/developers/funnel.md): Work with deals, pipelines, products, goals, reports and Outreach sequences from code or an agent, over REST or MCP, as the member whose People the deals link. - [Build on Venom Calendar](https://cloud.usevenom.dev/docs/developers/calendar.md): Work with a member's calendar from code or an agent. Find free times, book and move meetings, manage event types and schedules, send time offers and group polls over REST or MCP, and put booking pages on your own site. - [Build on Venom Comms](https://cloud.usevenom.dev/docs/developers/comms.md): Send messages and place phone calls from your app or an agent. Text people on SMS, WhatsApp, RCS, Telegram or email, run fallback profiles, read conversations and follow replies over the Comms API or MCP. - [Build on Venom Support](https://cloud.usevenom.dev/docs/developers/support.md): Read and triage the support inbox from code or an agent. Assign and tag conversations, add internal notes, draft replies from your notes and send them once a person approves, over REST or MCP. - [Build on Venom Chat](https://cloud.usevenom.dev/docs/developers/chat.md): Read channels and DMs, post and reply in threads, react, search, and follow chat with a change cursor from code or an agent, over REST or MCP. A team key joins as an agent member. - [Build on Venom Incidents](https://cloud.usevenom.dev/docs/developers/incidents.md): Triage errors, run incidents and manage on-call from code or an agent. Read and resolve error issues, declare and update incidents, page people and change alert rules over REST or MCP, and send errors from your apps with an SDK key. - [Build on the Status page](https://cloud.usevenom.dev/docs/developers/status.md): Manage the public status page from code or an agent. Add uptime checks, read their results, schedule maintenance, edit the listed services and manage subscribers over REST or MCP. - [Build on Venom Forms](https://cloud.usevenom.dev/docs/developers/forms.md): Build, preview, publish and close forms from code or an agent, read and export their responses, and send each response to Notes, Tasks, Slack, Funnel, Support, Calendar or your own webhook, over REST or MCP. - [Build on Venom Flags](https://cloud.usevenom.dev/docs/developers/flags.md): Create, target, roll out, evaluate and revert feature flags from code or an agent, over the Flags REST API, the SDK endpoints or MCP, and receive every flag change as a signed webhook. - [Build on Venom Experiments](https://cloud.usevenom.dev/docs/developers/experiments.md): Define metrics, propose, start, ramp, read and decide A/B tests and guarded rollouts on Venom Flags flags, run product analytics queries and send events, over the Experiments REST API, the event endpoint or MCP. - [Build on Org and teams](https://cloud.usevenom.dev/docs/developers/org.md): Read and manage the organisation's teams, subteams and team members from code or an agent, over REST or MCP, with the same rules as Settings, Teams. - [Build on Computers](https://cloud.usevenom.dev/docs/developers/computers.md): Give agents their own persistent browsers on your daemons from code or an agent. Create, start and stop computers, read what they did, ask a person to take over and manage a shared computer's agents over MCP. - [Build on Agents](https://cloud.usevenom.dev/docs/developers/agents.md): Start and drive chats with coding agents on your daemons' projects and with agents on your computers, from code or another agent, over MCP or REST. - [Build on Admin and the mesh](https://cloud.usevenom.dev/docs/developers/admin.md): Run the org's console admin pages from code or an agent (members, budgets, provider keys, routing, webhooks, alerts, audit, daemons and more) with your member role, and find the admin, client and daemon APIs. - [Build on Studio](https://cloud.usevenom.dev/docs/developers/studio.md): Make decks, pages and HTML pages from code or an agent. Create them from blocks and charts, change one slide or block by id, keep versions, and share by link over MCP and REST. ## The venom CLI - [The venom CLI](https://cloud.usevenom.dev/docs/cli.md): 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. - [Flags](https://cloud.usevenom.dev/docs/cli/flags.md): Every flag the venom command takes, venom's own and the ones it inherits from pi, with what each does and its default. - [Slash commands](https://cloud.usevenom.dev/docs/cli/slash-commands.md): Every slash command in a venom session, grouped by what it is for, with its arguments, plus the context commands in detail. - [Keys](https://cloud.usevenom.dev/docs/cli/keys.md): The leader key (ctrl+g) and what each key after it does, the direct shortcuts venom adds, pi's own keys, and copying text out of the TUI. - [The terminal UI](https://cloud.usevenom.dev/docs/cli/tui.md): What the venom TUI shows and how to change it, from the HUD, call meter, transcript verbosity and reading width to the agents panel, pull requests pane, attachments, sounds and colour themes. - [Plan mode](https://cloud.usevenom.dev/docs/cli/plan-mode.md): Have the agent investigate read-only and write a plan before it changes anything, then approve the plan and let it execute. - [Print, JSON and RPC modes](https://cloud.usevenom.dev/docs/cli/headless.md): Run venom without the TUI, in scripts, CI and other programs, with one printed answer, a JSON event stream or an RPC loop, plus piped stdin, approvals and --json output from subcommands. - [Sessions, resume and export](https://cloud.usevenom.dev/docs/cli/sessions.md): Where venom keeps sessions, how to continue, resume, search, replay, export, share and attach to them, and how to find the ones that went wrong. - [Workspaces (git worktrees)](https://cloud.usevenom.dev/docs/cli/workspaces.md): Run a session or a subagent in its own git worktree, then merge, apply, open a pull request for or remove its work with venom workspace. - [The agent's tools](https://cloud.usevenom.dev/docs/cli/tools.md): The tools the venom agent can call beyond reading, editing and running commands, when each is offered, what it can reach, and the tests it runs after edits. - [Cost, health and routing commands](https://cloud.usevenom.dev/docs/cli/insight-commands.md): The venom subcommands that check the setup and explain spend, routing, tool errors, wasted tokens, flaky tests and local models. - [Project setup, memory and onboarding commands](https://cloud.usevenom.dev/docs/cli/project-commands.md): Set a project up for venom, keep its memory, index its code, and help new people learn a codebase with tours, explanations and answers that cite their sources. - [Git, review and shipping commands](https://cloud.usevenom.dev/docs/cli/git-commands.md): Find the commit that broke a test, try a goal several ways at once, track intents, sign and verify who made a change, revert it, and ship a branch or a stack of them. ## Configuration - [Configuration](https://cloud.usevenom.dev/docs/configuration.md): Where venom reads its settings from, which file or variable wins, and how to see, check and change the configuration in force. - [venom.yaml reference](https://cloud.usevenom.dev/docs/configuration/venom-yaml.md): Every key venom.yaml accepts, with its type, default, the environment variable that overrides it and whether a project file needs trust. - [Gears](https://cloud.usevenom.dev/docs/configuration/gears.md): Switch the main model, thinking level, delegation models and route profile in one keystroke, use the built-in gears, and define your own. - [UI, themes and keys](https://cloud.usevenom.dev/docs/configuration/ui-and-themes.md): Set the TUI's reading width, transcript, HUD, statusline, colour theme, leader key and gear hotkeys in venom.yaml. - [Models, offline mode and tool billing](https://cloud.usevenom.dev/docs/configuration/models.md): Choose the main, delegation, vision and decision models and their thinking levels, point venom at an orchestrator, and configure offline mode, tool billing, tests after edits and learned skills. - [Environment variables](https://cloud.usevenom.dev/docs/configuration/env-vars.md): The VENOM_* environment variables the CLI reads, what each sets, its default, and the venom.yaml key it overrides. ## The harness library - [The harness library](https://cloud.usevenom.dev/docs/harness.md): What @venom/harness is, which package to use for your app, how to install it and where each part of the library is documented. - [Embed the harness](https://cloud.usevenom.dev/docs/harness/embedding.md): Run a first venom session from Node, from a Next.js route handler and from a background worker, with state kept where your app wants it. - [Sessions, events and cost](https://cloud.usevenom.dev/docs/harness/sessions.md): Every HarnessOptions and CreateSessionOptions field, the event stream a session emits, saved sessions and how to read a session's cost. - [Your own tools and approvals](https://cloud.usevenom.dev/docs/harness/tools-and-approvals.md): Give the agent app-specific tools with defineTool, decide every permission ask in your own code, and see how the permission engine treats your tools. - [@venom/harness/ws: a WebSocket server with no dependencies](https://cloud.usevenom.dev/docs/harness/ws.md): The server side of RFC 6455 for a node:http server's upgrade event, as used by the browser relay and the voice tests. - [The permission engine](https://cloud.usevenom.dev/docs/harness/permissions.md): Use @venom/harness/permissions to judge tool calls with venom's rules and modes, run commands in the OS sandbox and keep audit records, with or without a session. - [Model provider](https://cloud.usevenom.dev/docs/harness/providers.md): Point harness sessions at any OpenAI-compatible server, map venom's model aliases to real models, and understand the provider's errors and model discovery. - [Subagents and model tiers](https://cloud.usevenom.dev/docs/harness/subagents.md): How the agent delegates work to subagents through the task tool, which built-in agents ship, how model tiers pick cheaper models, and how writers get their own git worktrees. - [Claude Code compatibility, config and plugins](https://cloud.usevenom.dev/docs/harness/claude-code-compat.md): What a harness session reads from a project (CLAUDE.md, .claude/, .mcp.json, venom.yaml, plugins, templates), how trust gates it, and the library APIs behind each. - [Context, memory and the agent runtime](https://cloud.usevenom.dev/docs/harness/context-and-memory.md): How a session keeps its context small (masking, compaction, recall), carries memory between sessions, undoes file changes, and runs its agents as processes you can signal and suspend. - [Entry points](https://cloud.usevenom.dev/docs/harness/entry-points.md): Every import path of @venom/harness, what it is for and whether it loads pi, with the API of the modules that have no page of their own. - [Build a SaaS on the harness](https://cloud.usevenom.dev/docs/harness/saas-recipe.md): A worked design for a multi-tenant app on @venom/harness, using a collections back office as the example: tenancy, tools, human approvals, audit, cost caps and deployment. ## Server API (venom serve) - [Server API (venom serve)](https://cloud.usevenom.dev/docs/server-api.md): 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. - [Sessions](https://cloud.usevenom.dev/docs/server-api/sessions.md): Create, prompt, steer, abort, resume, hand off and close venom serve sessions, and read their transcript. - [Events (Server-Sent Events)](https://cloud.usevenom.dev/docs/server-api/events.md): Follow a venom serve session over Server-Sent Events, replay what you missed, and read the session, harness and server event types. - [Approvals and questions](https://cloud.usevenom.dev/docs/server-api/approvals-and-questions.md): Answer a venom serve session's permission requests and its ask_user questions from your own code, with timeouts, remembered rules and remote policies. - [Files, checkpoints and the browser IDE](https://cloud.usevenom.dev/docs/server-api/files-and-changes.md): Read each turn's file changes as before and after text, browse and edit a session's workspace over HTTP, and open the browser IDE that venom serve hosts. - [Agent processes](https://cloud.usevenom.dev/docs/server-api/agents.md): List a session's agent and subagent processes with their rates, signal one to pause, interrupt or stop it, and switch an agent's model mid-session. - [Schedules and workflows over HTTP](https://cloud.usevenom.dev/docs/server-api/schedules-and-workflows.md): List venom serve's scheduled background agents, start one now, read its runs and their output files, and list a workspace's workflow scripts. - [Inbox and phone approvals](https://cloud.usevenom.dev/docs/server-api/mobile-and-inbox.md): Read and answer the host's decision inbox over HTTP, pair a phone with the venom serve inbox page, and bridge the inbox to a Matrix room. - [Health, server proof and host reports](https://cloud.usevenom.dev/docs/server-api/operations.md): Check venom serve's health, fetch its OpenAPI document, verify a server holds the token before sending it, and read the gears, evidence and board reports. - [Python and TypeScript clients](https://cloud.usevenom.dev/docs/server-api/clients.md): Drive venom serve from Python with venom-client (sync and asyncio) or from TypeScript with HarnessClient, including run helpers, typed errors and reconnecting event streams. ## Orchestrator - [Orchestrator](https://cloud.usevenom.dev/docs/orchestrator.md): 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. - [Upstreams and kinds](https://cloud.usevenom.dev/docs/orchestrator/upstreams.md): Add an inference server or cloud provider to the orchestrator, pick its kind, and set its keys, models, capabilities and limits. - [Provider keys and setup](https://cloud.usevenom.dev/docs/orchestrator/providers-setup.md): Add API keys for cloud providers, local engine URLs and voice providers to a self-hosted orchestrator without editing .env. - [Routes and strategies](https://cloud.usevenom.dev/docs/orchestrator/routing.md): Define model aliases, choose how their targets are ordered, and understand fallback, retries, stickiness, experiments and shadow traffic. - [Profiles, side requests and gears](https://cloud.usevenom.dev/docs/orchestrator/profiles-and-gears.md): Re-target aliases per request with route profiles, give side requests their own body defaults, and publish gears that clients list. - [Configuration reference](https://cloud.usevenom.dev/docs/orchestrator/configuration.md): Every top-level section of orchestrator.yaml with its keys and defaults, plus how the file is loaded, reloaded, versioned and rolled back. - [Orchestrator environment variables](https://cloud.usevenom.dev/docs/orchestrator/environment.md): Every environment variable the orchestrator, its shipped config, the desktop daemon and the public-mesh auditor read, with defaults. - [Chat, responses, embeddings and models](https://cloud.usevenom.dev/docs/orchestrator/chat-and-responses.md): Call chat completions, completions, the Responses API (including background responses) and embeddings through the orchestrator, and read what the model list tells you. - [Keys, budgets and limits](https://cloud.usevenom.dev/docs/orchestrator/keys-and-budgets.md): Mint client keys, limit what each may call and spend, cap intents and teams, and let each key read its own usage and routing. - [Batches, files and service tiers](https://cloud.usevenom.dev/docs/orchestrator/batches-and-files.md): Run offline work with OpenAI's Batch API, turn single requests into batch requests at batch prices, upload files, and ask for flex or priority tiers. - [Rerank, images and decisions](https://cloud.usevenom.dev/docs/orchestrator/rerank-images-decisions.md): Rerank documents, generate images and ask typed decision questions through the orchestrator's routing, keys and budgets. - [Web search and MCP](https://cloud.usevenom.dev/docs/orchestrator/search-and-mcp.md): Give agents web search over backends you choose, with the search keys kept on the server, through POST /v1/search or as an MCP server for other tools. - [Admin API](https://cloud.usevenom.dev/docs/orchestrator/admin-api.md): Read the orchestrator's live state, request log, sessions, spend, cache and pricing reports, and manage keys and config over /admin/v1. - [Operations - probes, metrics, local models and mesh](https://cloud.usevenom.dev/docs/orchestrator/operations.md): Monitor the orchestrator with health probes, Prometheus metrics and the profiler, manage local models, connect it to Venom Cloud, and replay traffic from cassettes. ## Voice - [Voice](https://cloud.usevenom.dev/docs/voice.md): Speak to venom and have it speak back, through your own speech models or cloud ones, behind one OpenAI-shaped audio API. - [Voice in the venom CLI](https://cloud.usevenom.dev/docs/voice/cli-voice.md): Dictate into the editor with /voice or ctrl+g r, and have answers read aloud with /speak or ctrl+g k. - [The orchestrator's audio API](https://cloud.usevenom.dev/docs/voice/speech-api.md): Generate speech, list voices and transcribe audio through the orchestrator, route it to local or cloud speech models, and price it per character or per second. - [Voice agents: the core library](https://cloud.usevenom.dev/docs/voice/agents-core.md): The @venom/voice package, the call pipeline under venom's AI phone agents, and how to build and test it. - [Voice in the harness](https://cloud.usevenom.dev/docs/voice/harness-voice.md): The @venom/harness/voice client (speak, listVoices, transcribe, translate), the agent's speak and transcribe tools, and venom.yaml's voice keys. - [Local speech models](https://cloud.usevenom.dev/docs/voice/local-speech.md): Run CosyVoice, Qwen3-TTS, IndexTTS, Spark-TTS, Fish Speech and other open speech models on your own hardware and use them through the orchestrator's OpenAI-shaped audio API, voice cloning included. - [Realtime transcription](https://cloud.usevenom.dev/docs/voice/realtime-transcription.md): Stream audio to the orchestrator over a WebSocket and get transcripts back as you speak, with OpenAI's realtime transcription events, in front of local or cloud speech models. - [ElevenLabs, Fish Audio and BytePlus Seed Speech](https://cloud.usevenom.dev/docs/voice/cloud-speech-providers.md): Route text to speech and transcription to ElevenLabs, Fish Audio or BytePlus Seed Speech through the orchestrator's OpenAI-shaped audio API. - [Qwen, MiniMax and Mistral speech](https://cloud.usevenom.dev/docs/voice/cloud-speech-qwen-minimax-mistral.md): Route speech to Qwen TTS on Model Studio and MiniMax T2A, and transcription to Mistral's Voxtral, through the orchestrator's audio API. - [Voice agents: calls in venom serve](https://cloud.usevenom.dev/docs/voice/calls.md): Configure voice agents in venom.yaml, take calls on the browser test line, and read each call's events, transcript and recording over the calls API. ## Security - [Security](https://cloud.usevenom.dev/docs/security.md): 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. - [Permission modes and rules](https://cloud.usevenom.dev/docs/security/permissions.md): Choose a permission mode, write allow, ask and deny rules, and understand the order in which venom judges every tool call. - [OS sandbox and network allowlist](https://cloud.usevenom.dev/docs/security/sandbox.md): What sandboxed bash can read, write and reach on macOS and Linux, and how to change its network allowlist. - [Project trust](https://cloud.usevenom.dev/docs/security/trust.md): Decide whether a project's own hooks, MCP servers, allow rules and loosening settings may run, from the TUI dialog or headless with venom trust. - [Organisation policy and risk tiers](https://cloud.usevenom.dev/docs/security/policy.md): Enforce rules for every venom on a machine with /etc/venom/policy.json or a signed policy from Venom Cloud, and score the risk of a change with venom risk. - [Secrets vault](https://cloud.usevenom.dev/docs/security/secrets.md): Store tokens once with venom secrets set, let the agent use them as {{secret:NAME}} without ever seeing the value, and bind each one to the origins it may reach. - [Guardrails](https://cloud.usevenom.dev/docs/security/guardrails.md): Set content, routing, model, tool, spend and answer rules at the org, key group and member layer, read a guardrail code, and use the prompt-injection shield and supply-chain check. - [Session guard and runaway guards](https://cloud.usevenom.dev/docs/security/session-guard.md): Pause sessions that stall, loop or overspend, set time and dollar caps with session_guard, and set an output budget with guards. - [Audit log, signed actions and compliance](https://cloud.usevenom.dev/docs/security/audit.md): Verify the hash-chained permission audit log, the signed log of every command and file write, offline audit exports and Venom Cloud compliance packs. - [Network egress map](https://cloud.usevenom.dev/docs/security/egress.md): See which hosts each session contacted through bash, the browser, web tools and MCP, with hosts outside the allowlist or new for the repository flagged. - [Red team](https://cloud.usevenom.dev/docs/security/redteam.md): Run the versioned attack corpus against your guardrails and a gear with venom redteam run, within a spend cap, and read which guardrail caught each case. ## Automation - [Automation](https://cloud.usevenom.dev/docs/automation.md): 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. - [Workflows](https://cloud.usevenom.dev/docs/automation/workflows.md): Script a multi-agent pipeline in JavaScript, check it in next to the code, and run it with venom workflow run or /workflow with a spend cap, resume and per-agent worktrees. - [Background agents](https://cloud.usevenom.dev/docs/automation/background.md): Hand a goal to a background agent in its own worktree with venom do, see a cost forecast first, and let a machine work through the Linear and Jira issues your org assigns with venom intake. - [The inbox](https://cloud.usevenom.dev/docs/automation/inbox.md): Answer every decision your agents are waiting on from one ranked queue with venom inbox, set an attention budget, route items to code owners, and answer from your phone, a Matrix room or HTTP. - [Plan then execute](https://cloud.usevenom.dev/docs/automation/plan-execute.md): Have the main model write a plan with a check per step, approve or edit it, then let cheap workers carry out each step while the main model verifies it with /plan-exec. - [Spec to pull requests](https://cloud.usevenom.dev/docs/automation/spec-to-pr.md): Turn a design doc or a GitHub issue into a stack of small, reviewed pull requests with venom spec, then keep the stack current as earlier slices merge. - [Contract-first work between agents](https://cloud.usevenom.dev/docs/automation/contract-first.md): Split a change that spans two components into a contract slice and two parallel slices, so a producer and a consumer agent never wait on each other. - [Scheduled agents](https://cloud.usevenom.dev/docs/automation/schedules.md): Run background agents from venom serve on a cron or on events, each in a fresh git worktree with a spend and time cap, using built-in roles, plugin roles or recorded browser tasks. - [Long tasks and resume](https://cloud.usevenom.dev/docs/automation/long-tasks.md): Keep hours-long runs alive through crashes, reboots and provider usage limits with checkpoints and venom resume, and let the stuck detector shift gears or stop a run that loops. - [Code review](https://cloud.usevenom.dev/docs/automation/review.md): Review a diff, a GitHub pull request or a GitLab merge request read-only with venom review or /review, post the findings, watch a repository, and have the agent review itself before it opens a pull request. - [The review action](https://cloud.usevenom.dev/docs/automation/review-action.md): Review every pull request with venom review on a cheap gear from GitHub Actions or GitLab CI, with inline comments, one summary comment with the cost, and a spend cap. - [Replay a session on another model](https://cloud.usevenom.dev/docs/automation/replay.md): Re-run a recorded session's prompts against another model, gear or route profile in a scratch workspace with venom replay, and compare turns, tokens, cost, tools and a check command. - [Teams of agents](https://cloud.usevenom.dev/docs/automation/teams.md): See your and your teammates' agents with venom fleet, hand a session to a teammate or another host with venom handoff, coordinate subagents on the shared board, and drive agents from your issue tracker with venom board. - [Tasks and delegation](https://cloud.usevenom.dev/docs/automation/tasks.md): Count a session's spend toward a pull request, issue or tracker key with --task, /task and VENOM_TASK, and let the agent delegate work to subagents with the task tool. ## Plugins and extensions - [Plugins and extensions](https://cloud.usevenom.dev/docs/plugins.md): Extend venom with plugins, pi packages, Claude Code plugins, hooks, sounds, skills, MCP servers, themes, templates and roles. - [Install and manage plugins](https://cloud.usevenom.dev/docs/plugins/installing.md): Add plugins from a directory, npm, git or your org's marketplace, turn them on and off, configure them and see why one did not load. - [Write a plugin](https://cloud.usevenom.dev/docs/plugins/writing.md): Scaffold, write, test and publish a venom plugin with tools, commands, leader keys, block renderers, HUD fields and panel sections. - [Claude Code plugins and pi packages](https://cloud.usevenom.dev/docs/plugins/claude-code-plugins.md): Load Claude Code plugins and pi packages in venom as they are, and see which parts of their formats venom supports. - [Hooks and venom's events](https://cloud.usevenom.dev/docs/plugins/hooks.md): Run a command or play a sound when the agent finishes, fails, needs approval or completes a step, and use Claude Code's hooks as they are. - [Sounds](https://cloud.usevenom.dev/docs/plugins/sounds.md): Hear when venom is done, failed or needs approval, pick or replace the sounds, set quiet hours and choose the player. - [Skills and slash commands](https://cloud.usevenom.dev/docs/plugins/skills.md): Add skills the agent loads on demand and slash commands from markdown files, list what is loaded, and find skills the agent asked for but did not have. - [MCP servers](https://cloud.usevenom.dev/docs/plugins/mcp.md): Give the agent tools from MCP servers in Claude Code's .mcp.json format, and use your organisation's approved servers with sign-in and tool pins. - [Themes](https://cloud.usevenom.dev/docs/plugins/themes.md): Pick one of venom's sixteen colour themes, tweak one, write your own theme file or ship themes in a plugin. - [Session templates and learned templates](https://cloud.usevenom.dev/docs/plugins/templates.md): Start a session from a saved setup (prompt, gear, mode, tools, checks) and save jobs you repeat as templates. - [Team library](https://cloud.usevenom.dev/docs/plugins/library.md): Use your organisation's shared prompts as /org commands and its skills in every session, offline from a cache, and hide what you do not want. - [Plugin roles](https://cloud.usevenom.dev/docs/plugins/roles.md): Install a standing agent a plugin ships (cron, prompt, mode, budget) as a reviewed schedule entry that venom serve runs. - [Terminal charts](https://cloud.usevenom.dev/docs/plugins/charts.md): Draw bar, line, area, scatter, sparkline, histogram, heatmap, pie, gauge and timeline charts in the terminal from a small YAML or JSON spec. - [Pull requests pane](https://cloud.usevenom.dev/docs/plugins/pr-pane.md): Browse the repository's open pull requests beside the chat and approve, comment, request changes or merge through the GitHub CLI. - [venom-board, GitHub issues as an agent control plane](https://cloud.usevenom.dev/docs/plugins/venom-board.md): Run a GitHub issue board where agents file ranked proposals, an owner approves with labels, and agents build, gate and merge what was approved. ## Integrations - [Integrations](https://cloud.usevenom.dev/docs/integrations.md): 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. - [Python client (venom-client)](https://cloud.usevenom.dev/docs/integrations/python-client.md): 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](https://cloud.usevenom.dev/docs/integrations/vscode.md): 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)](https://cloud.usevenom.dev/docs/integrations/acp-zed.md): 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](https://cloud.usevenom.dev/docs/integrations/browser-extension.md): 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](https://cloud.usevenom.dev/docs/integrations/slack-and-trackers.md): 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)](https://cloud.usevenom.dev/docs/integrations/globe-mcp.md): 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](https://cloud.usevenom.dev/docs/integrations/auto-ontology-mcp.md): 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. ## Venom Cloud - [Venom Cloud](https://cloud.usevenom.dev/docs/cloud.md): What Venom Cloud is, how its console is laid out, which role opens which page, and where the console and API guides start. - [The Venom workspace, search and shortcuts](https://cloud.usevenom.dev/docs/cloud/workspace.md): Move between Notes, Tasks, Flags, Experiments and Admin with the app rail, find anything with one ⌘K search, and learn the keyboard shortcuts that work in every app. - [Quick search (⌘K) across every app](https://cloud.usevenom.dev/docs/cloud/quick-search.md): How ⌘K finds notes, issues, people, deals, flags, support tickets, chat and more in one search, what each app matches, how results are ranked, and the streamed search API behind it. - [References and links between items](https://cloud.usevenom.dev/docs/cloud/references.md): Point at any item in the workspace (issues, notes, people, deals, incidents, tickets, forms, flags, chats, computers, Studio decks and pages and more) with one reference, open it from a pasted link, and link items across products. - [Home, the shared inbox and onboarding](https://cloud.usevenom.dev/docs/cloud/home.md): Use Home to pick up recent notes and issues, see what is assigned to you, open your apps, and get started; read the bell's shared inbox; and know what the welcome step, first-visit cards and tour do. - [Sign in to the console and the CLI](https://cloud.usevenom.dev/docs/cloud/console-sign-in.md): Sign in to the Venom Cloud console with email, GitHub, single sign-on or the operator token, create your first organisation, and approve a venom cloud login from the terminal. - [Console home, Get started and onboarding paths](https://cloud.usevenom.dev/docs/cloud/console-home.md): Read the console's Overview, finish the first-run checklist on Get started, build onboarding paths for new members, look up a guardrail code and ask your organisation's knowledge. - [Drafts, everything waiting for your approval](https://cloud.usevenom.dev/docs/cloud/drafts.md): Review every message Venom drafted for you in one list under Home. It covers Outreach drafts, messages your bots hold, People's morning queue, Support drafts and intro asks, with approve, edit, hold and skip, and a tool for agents. - [Organisations, members and roles](https://cloud.usevenom.dev/docs/cloud/console-orgs-members.md): Create and switch organisations, invite members, change their roles, understand what each role may do, and set a key group's permission profile for the venom CLI. - [Teams, subteams and roles](https://cloud.usevenom.dev/docs/cloud/teams.md): How Venom Cloud models an org's teams, subteams, members and roles once for every product, what an org role allows in each product, and how today's Tasks teams and Notes team vaults fit in. - [Single sign-on and SCIM](https://cloud.usevenom.dev/docs/cloud/console-sso.md): Connect your organisation to Okta, Microsoft Entra ID, Google Workspace or any OIDC or SAML 2.0 identity provider, map groups to roles, require SSO and provision members with SCIM. - [API keys and key rotation](https://cloud.usevenom.dev/docs/cloud/console-api-keys.md): Create vck_ API keys for the venom CLI, scripts and OpenAI SDKs, scope them by model, budget, rate and expiry, rotate, pause and revoke them, and set the organisation's key rotation schedule. - [Languages](https://cloud.usevenom.dev/docs/cloud/languages.md): Use Venom Cloud in Bahasa Indonesia, Simplified or Traditional Chinese, Cantonese, Japanese or Korean, and how translations are added without making pages heavier. - [Providers and provider keys](https://cloud.usevenom.dev/docs/cloud/console-providers.md): Connect your own OpenAI, Anthropic, Mistral, MiniMax and other provider keys to Venom Cloud, choose the models each key serves, rotate keys and watch how each provider serves you. - [Organisation gears](https://cloud.usevenom.dev/docs/cloud/console-gears.md): Define the gears every venom CLI user in your organisation sees, pick a model and route for each role, set the default gear and lock members to your gears. - [Routing, failover drills, local autopilot and shadow tests](https://cloud.usevenom.dev/docs/cloud/console-routing.md): Decide which model answers and where it runs, rehearse an outage without sending traffic, move paid work to your own models, and try a candidate model on real requests before you switch. - [Pricing and invoice reconciliation](https://cloud.usevenom.dev/docs/cloud/console-prices.md): See and set the price Venom Cloud books for each model, pick where prices come from, check providers for new models and prices, and compare a provider's bill with what Venom booked. - [Budgets and spend guards](https://cloud.usevenom.dev/docs/cloud/console-budgets.md): Set daily, monthly or lifetime spend limits per member, API key, key group, gear or project that warn first, then block requests or switch them to a cheaper model. - [AI spend](https://cloud.usevenom.dev/docs/cloud/ai-spend.md): See every daily AI limit in your organisation on one page, with a bar for what each product spent today, and change any of them in place if you are an owner or admin. - [Usage, savings and chargeback](https://cloud.usevenom.dev/docs/cloud/console-usage.md): Read your organisation's spend and volume, set the monthly spend cap, see cost per task and per project, find savings, and produce chargeback statements per key group, project, gear, key or member. - [Requests and request traces](https://cloud.usevenom.dev/docs/cloud/console-requests.md): Search every request your organisation sent through Venom Cloud, open one request's trace, read its stored prompt and response, and set how long content is kept. - [Log query language](https://cloud.usevenom.dev/docs/cloud/console-log-query.md): Search, filter, group and chart your organisation's request log with one line, in the console's Requests page, alerts, the live feed and the admin API. - [Sessions, live feed and activity](https://cloud.usevenom.dev/docs/cloud/console-sessions.md): Watch requests as they finish, see who is online, and open your team's agent sessions in the console, whether remote, shared, captured from the request log, handed off or shared live. - [Claude Code sessions in Venom](https://cloud.usevenom.dev/docs/cloud/claude-code-sessions.md): Install the Venom plugin for Claude Code so each finished session shows up in Session history and feeds the Inbox of Venom Notes, redacted on your machine and sent only to your own cloud. - [Failures and jobs](https://cloud.usevenom.dev/docs/cloud/console-failures.md): Find out what made agent sessions and requests fail, grouped by cause with example sessions, and inspect the relayed jobs the cloud dispatched to daemons. - [Alerts and notifications](https://cloud.usevenom.dev/docs/cloud/console-alerts.md): Run saved log searches every 5 minutes with a signed webhook, and read the notification inbox for budget thresholds, spend forecasts, spend anomalies and key rotation. - [Skills in the Venom plugin for Claude Code](https://cloud.usevenom.dev/docs/cloud/claude-code-skills.md): The skills that come with the Venom plugin for Claude Code, in every project once it is installed - plain writing, two management audits, doc sync, Linear plans, RCAs, cloud migrations, security audits, technical due diligence and Venom Studio artifacts. - [Audit log and audit export](https://cloud.usevenom.dev/docs/cloud/console-audit.md): Search your organisation's audit log, see what each change did, undo a settings change, download the log, and copy it to your own S3-compatible bucket on a schedule. - [Guardrails and filters in the console](https://cloud.usevenom.dev/docs/cloud/console-guardrails.md): Set the org's, key groups' and your own guardrails, test them on pasted text, and manage the prompt and response filters and the secret scanner from the Venom Cloud console. - [Team library and starter packs](https://cloud.usevenom.dev/docs/cloud/console-library.md): Publish prompts and skills your members get in venom, version and roll them back, and install a vertical starter pack from the Venom Cloud console. - [Org skills registry](https://cloud.usevenom.dev/docs/cloud/console-skills.md): Keep your organisation's reusable agent skills in one place in Venom Cloud, add them from a GitHub repository, by upload or by writing them, turn each on or off, change several at once, approve updates from their source, and roll back to any version. - [Marketplace and MCP servers](https://cloud.usevenom.dev/docs/cloud/console-marketplace.md): Submit, review and pin plugins, skills and MCP server packages in your org's marketplace, and approve the MCP servers each key group's venom users get. - [Your organisation's MCP servers](https://cloud.usevenom.dev/docs/cloud/custom-mcp-servers.md): Add your own MCP servers by URL for everyone in the organisation, test the connection, choose whether the cloud or only your venom clients reach them, and keep credentials sealed. - [Org memory](https://cloud.usevenom.dev/docs/cloud/console-memory.md): Keep the short facts your team agrees on in Venom Cloud, review what members propose, and see the exact block venom loads into a session for a repository and key group. - [Evals and experiments](https://cloud.usevenom.dev/docs/cloud/console-evals.md): Run the eval suite or your own golden tasks against your gears on a runner you control, and A/B test two gears or two prompt versions on live sessions from the Venom Cloud console. - [Model quality, scorecard and red team](https://cloud.usevenom.dev/docs/cloud/console-quality.md): Schedule quality checks on the models your gears use, catch drift and swap degraded models, read the agent scorecard per gear or key group, and run the red-team suite from the console. - [Customers, invoices and the customer portal](https://cloud.usevenom.dev/docs/cloud/console-customers.md): Resell model access to your own customers with their own keys, prices, limits, budgets, invoices, SLAs and a branded usage page. - [Venom Tasks planning](https://cloud.usevenom.dev/docs/cloud/tasks-planning.md): Plan work in Venom Tasks with projects, milestones and updates, a drag-to-reschedule timeline, team cycles with a burn-up chart, saved views, and team and workspace settings. - [Import issues into Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-import.md): Move a whole Linear workspace into Venom Tasks from one API key, in the background, and sync it again later; or bring issues from Linear, Jira, GitHub, Asana, Trello or Lark into one team with a mapping and a dry run. - [MSP mode and the partner portal](https://cloud.usevenom.dev/docs/cloud/console-msp.md): Manage many client organisations from one Venom Cloud org, with each client's consent, a ceiling role, scopes and an end date. - [Export from Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-export.md): Take your data out of Venom Tasks as CSV for any list, project or initiative, or as a ZIP of CSV and JSON for the whole workspace, with the exact columns and the JSON schema, who may export what, and how an agent does it. - [Link GitHub pull requests to Venom Tasks issues](https://cloud.usevenom.dev/docs/cloud/tasks-github.md): Connect a GitHub webhook so pull requests and commits that name an issue key show on the issue, move issues through draft, open, review, ready to merge and merged by each team's rules and target-branch rules, comment back on the pull request, and start an issue when you copy its branch name. - [Recurring issues in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-recurring.md): Make an issue on a schedule in Venom Tasks, daily, weekly on chosen days, monthly or every few weeks, in your time zone, with pause, resume, an end date and an option to skip while the last one is open. - [Subteams in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-subteams.md): Nest teams under a parent team, see a parent's work with its subteams' issues, choose what a subteam takes from its parent, and change a team's settings from the sidebar's team menu. - [Venom Tasks settings](https://cloud.usevenom.dev/docs/cloud/tasks-settings.md): Settings in Venom Tasks has a left nav with your own Preferences and Notifications, workspace pages for teams, members, labels and import, and one page per team with a danger zone. - [Integrations - Slack, Linear and Jira](https://cloud.usevenom.dev/docs/cloud/console-integrations.md): Connect your own Slack app so @venom answers in threads, and your Linear or Jira so labelled issues become pull requests from runners you control. - [Links and attachments on Tasks issues and projects](https://cloud.usevenom.dev/docs/cloud/tasks-resources.md): Add web links to an issue or a project, and attach files to an issue, including large ones, kept in the files of Notes. - [SLAs in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-sla.md): Give a team's issues a deadline by priority and label, in hours, days, business hours or business days, counted from creation or from leaving Triage; see the time left on every list, board and issue, get told when one is at risk or breached, filter by it and chart breaches in Insights. - [Triage rules in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-triage-rules.md): Route new issues as they land in a team's Triage, by label, creator, source, text or priority, and set their team, status, assignee, agent, labels, priority, project or cycle; ordered, first match wins, recorded on the issue. - [Venom Tasks notifications](https://cloud.usevenom.dev/docs/cloud/tasks-notifications.md): Quiet hours that hold push and email until morning, notifications that open the comment they are about, muting one comment thread, the email when a workspace export is ready, and agent chats you started from an issue reporting back in your Inbox. - [Customer requests in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-customer-requests.md): Link Support conversations, People companies and Funnel deals to issues and projects as customer requests, see who asked and what it is worth, and sort, filter and chart issues by that demand. - [Daemons, nodes, fleet, autoscaling and model lifecycle](https://cloud.usevenom.dev/docs/cloud/console-daemons.md): Connect and run your own daemons, trust public nodes, see your org's agents, rent GPUs on demand and keep gears ahead of retiring models. - [Releases in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-releases.md): Say what ships together with release pipelines and releases, fill them from GitHub pushes or any CI with a pipeline key, mark them shipped when GitHub reports a deployment, write release notes from a template, and copy each pipeline's changelog as Markdown. - [Organisation settings](https://cloud.usevenom.dev/docs/cloud/console-settings.md): The Settings area of the Venom Cloud console - plan and billing, backup and restore, compliance packs, webhooks, the public status page and public session links. - [The public site, downloads and docs routes](https://cloud.usevenom.dev/docs/cloud/cloud-site.md): What the public pages of Venom Cloud serve without a sign-in - the site, stable download links, the cloud status page and the docs in HTML, markdown and llms.txt. - [Self-hosting Venom Cloud](https://cloud.usevenom.dev/docs/cloud/self-hosting.md): Run your own Venom Cloud on Vercel and Neon, or locally for development, with every environment variable and make target it reads. - [Editing in Notes](https://cloud.usevenom.dev/docs/cloud/globe-editing.md): How Venom Notes stores a note as markdown that opens in Obsidian unchanged, and which syntax each kind of block and formatting becomes. - [Notes team vaults](https://cloud.usevenom.dev/docs/cloud/globe-team-vaults.md): Give one of your organisation's teams a shared Notes vault, see who opens it (subteams included), close it when it is empty, and share notes with a team. - [Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks.md): Track issues in Venom Cloud with teams, triage, a list and a board, an issue page, the command menu and keyboard shortcuts, and hand work to agents as delegates. - [Initiatives in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-initiatives.md): Group projects under an initiative, nest initiatives, and read their roll-up, timeline and status updates, with keys for each. - [Project updates and milestones in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-projects.md): An update schedule with reminders and nudges for the lead, "update missing" on the list, the page and Pulse, editing and deleting updates, comments and reactions on them, a summary of what changed, an initiative's feed with its projects' updates, and milestones with descriptions and drag-to-reorder. - [Insights in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-insights.md): Chart any list, board, project, cycle or saved view by issue count, effort, SLA breaches, cycle time, lead time, triage time, age or time in each status, sliced and segmented by a field, see its cumulative flow, and open the issues behind a bar. - [Pulse in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-pulse.md): One feed of the status updates of the projects and initiatives you lead, work on or follow, with health changes highlighted, the ones overdue for an update, and a weekly digest in the bell and by email. - [Dashboards in Venom Tasks](https://cloud.usevenom.dev/docs/cloud/tasks-dashboards.md): Save an Insights chart with a name, keep it private or share it with the org, and see your saved insights as a grid of live charts on the Dashboards page or inside a Notes page. - [Venom Flags](https://cloud.usevenom.dev/docs/cloud/flags.md): Put features behind flags in Venom Cloud, target users and segments, roll out by percentage per environment, review every change before it saves, and revert anything from the history. - [Status page uptime checks, maintenance and subscribers](https://cloud.usevenom.dev/docs/cloud/status-page.md): Watch your own services from the cloud with http, TCP and heartbeat checks, feed the status page's uptime bars and response-time charts, page on-call when a check keeps failing, schedule maintenance, and let readers follow by RSS, Atom or a signed webhook. - [Venom Forms](https://cloud.usevenom.dev/docs/cloud/forms.md): Build forms in Venom Cloud with a Tally-style builder, conditional logic and a live preview. Publish a link, and let agents build, change and publish them too. - [Forms logic, outlines and instructions](https://cloud.usevenom.dev/docs/cloud/forms-logic.md): How Venom Forms decides which questions a respondent sees, the markdown outline that creates a form, and the instructions that edit one safely. - [Share a form and take responses](https://cloud.usevenom.dev/docs/cloud/forms-sharing.md): The public form page, embeds (inline, popup, slider), file uploads, hidden fields from the link, and the local spam defences that need no third-party CAPTCHA. - [Form responses](https://cloud.usevenom.dev/docs/cloud/forms-responses.md): Read what came in: a table with a column per question, filters, a detail drawer, a summary with charts and drop-off by question, CSV export, retention, a feed of every form, and submits from your own backend over REST and MCP. - [Send form responses to Notes, Tasks, Funnel, Support, Calendar, webhooks and Slack](https://cloud.usevenom.dev/docs/cloud/forms-destinations.md): Connect a form to seven destinations, from a Notes database row to a Funnel deal or a booking link. Deliveries run after the response is saved, retry on failure and keep a log. - [Venom People](https://cloud.usevenom.dev/docs/cloud/people.md): Remember everyone you meet in Venom Cloud. Keep who they are, how you met, what you talked about and an AI context card per person, search by what you remember, and share people with your team without sharing your notes. - [Capture people in ten seconds](https://cloud.usevenom.dev/docs/cloud/people-capture.md): Add the people you meet to Venom People from your phone in about ten seconds. Scan a business card or badge, share a contact or screenshot from WhatsApp or Telegram, dictate or type a note, and let the event tag itself. - [Reach in Venom People](https://cloud.usevenom.dev/docs/cloud/people-reach.md): Name a topic, a territory and the kind of person you want, and Reach ranks your own people by fit, seniority and how you can reach them, says why for each, and puts them into a pipeline or a sequence in one go. - [Venom People for agents (MCP and REST)](https://cloud.usevenom.dev/docs/cloud/people-mcp.md): Let an agent search the people you know, add people, log interactions, read context cards, and list events and companies, through the workspace MCP server or its REST twin. - [Attachments on a person](https://cloud.usevenom.dev/docs/cloud/people-attachments.md): Keep images, files and links with someone in Venom People. Links show as cards with the service's mark and a title made from the address; nothing is fetched from the linked site. - [Keep your network warm in Venom People](https://cloud.usevenom.dev/docs/cloud/people-keep-warm.md): Debrief an event in a card stack, get five people a day to reach out to with a drafted message in your tone, set circles and cadences, see why each score is what it is, and ask who you know. Venom drafts; you press send. - [Notes databases for agents (MCP and REST)](https://cloud.usevenom.dev/docs/cloud/globe-databases-mcp.md): Let an agent create a database (table) inside a Notes page with its columns and rows, query it, change its schema and views, import CSV, and delete it cleanly, through the workspace MCP server or its REST twin. - [The Telegram bot for People](https://cloud.usevenom.dev/docs/cloud/people-telegram.md): Connect your organisation's own Telegram bot to Venom People. Forward a contact, a business card photo, a vCard or a voice note to it and the person lands in People, tagged with the day's event. - [Ask for an intro in Venom People](https://cloud.usevenom.dev/docs/cloud/people-intros.md): Ask one of your own contacts for an intro. Venom drafts the ask and a note to forward, tracks it to introduced, reminds you to nudge, and links it to a Funnel deal. It sends only when you press Send through Venom, one message per press. - [Mention People contacts in Notes](https://cloud.usevenom.dev/docs/cloud/globe-mentions.md): Type @ in a note to mention a contact from Venom People, see the notes that mention a person on their page, log a note as a meeting, and how agents read a mention. - [Notes pages for agents (trash, versions, sharing, comments, inbox)](https://cloud.usevenom.dev/docs/cloud/globe-pages-mcp.md): Notes tools beyond reading and writing notes, on the workspace MCP server and its REST twin. Trash, versions, publishing, sharing, links, favourites, comments, the Inbox, sources, files, settings, imports and database templates. - [Share people and find warm intros in Venom People](https://cloud.usevenom.dev/docs/cloud/people-network.md): Share a person, a selection or a whole circle with a team or the organisation, search who in the org knows someone at a company, see the warm-intro paths ranked by strength, and ask a colleague for an intro. Colleagues see that you know someone, never your notes. - [Import contacts into Venom People](https://cloud.usevenom.dev/docs/cloud/people-import.md): Bring in people from files you already have, Google Contacts, iCloud and Google vCards, LinkedIn connections, WhatsApp and Telegram exports, HubSpot and Pipedrive, with a review that merges duplicates and history that seeds relationship strength. - [Link people and companies in Venom People](https://cloud.usevenom.dev/docs/cloud/people-connections.md): Link one of your people to another with a kind and a date, record where someone has worked, and accept suggested links, all private to you and shown from both sides. - [Venom Funnel](https://cloud.usevenom.dev/docs/cloud/funnel.md): A sales pipeline on top of Venom People. Move deals through stages on a board, link the people involved with their context cards, track products, goals and the weighted forecast, and let agents do the same over MCP. - [Your network as a graph in Venom People](https://cloud.usevenom.dev/docs/cloud/people-graph.md): See you, every one of your people and their companies as a graph, with the links between people, why two people are connected, the People list's filters, colour and size by derived fields, a panel for what you select, focus, freeze, clusters, and people like someone. - [Import from Funnel](https://cloud.usevenom.dev/docs/cloud/funnel-import.md): Bring an existing Funnel database into Venom. The export format (one CSV per table or one JSON file), how contacts become People, what is matched and what is created, and what a re-import does. - [Public controversy check in People](https://cloud.usevenom.dev/docs/cloud/people-controversy.md): Turn on an optional check that flags people in Venom People who also appear on CancelPeople.com, with a neutral summary and things to watch out for when engaging. Off by default; names are matched on your server and never sent to the site. - [Enrich people and their photos](https://cloud.usevenom.dev/docs/cloud/people-enrichment.md): Optional enrichment for Venom People. "Enrich" on a person, or on many at once, asks the providers your organisation picks (Gravatar, Venom Search, Brave Search, People Data Labs, Apollo) for public facts and a photo, shown as suggestions you apply. Off by default; official APIs only. - [Classify people in People](https://cloud.usevenom.dev/docs/cloud/people-classification.md): Let the org's own model sort everyone in Venom People by sector, persona, seniority and opportunity, judge how relevant each person is to your focus, and search and sort by it, under a daily $ cap. - [Meetings in People](https://cloud.usevenom.dev/docs/cloud/people-meetings.md): A one-page brief on each person before a meeting, your next meetings on Today with their people, an after-meeting note that proposes the deal move, field updates and next step, and the Granola sync that files each meeting for you. - [Venom Chat](https://cloud.usevenom.dev/docs/cloud/chat.md): Team chat where people and agents are members. Public and private channels, DMs and group messages, threads, reactions, pins, search, live updates, and notifications in the same bell as the rest of Venom. - [Product feeds in Venom Chat](https://cloud.usevenom.dev/docs/cloud/chat-feeds.md): Post Incidents, Tasks, Flags, Experiments and Forms events to a channel as messages with buttons. Acknowledge a page or approve a flag change from the channel, with your own permissions. - [The overnight queue in People](https://cloud.usevenom.dev/docs/cloud/people-overnight.md): Switch a saved Reach view to run every night and find the people it picked on Today each morning, each with the reason and a drafted message to approve, edit or skip. Venom sends nothing unless you set a bot to. - [Agents in Venom Chat](https://cloud.usevenom.dev/docs/cloud/chat-agents.md): Add the Venom agent, or a service agent from Venom Tasks, to a channel and mention it; its answer streams into the thread. A channel owner picks its tools, including read access to the other Venom products, which run as you; a write waits for your Confirm. - [Signals in People](https://cloud.usevenom.dev/docs/cloud/people-signals.md): For each of your people, Venom reads your notes, interactions and deals and gives a call (engage, progress, hold or drop), strengths, weaknesses and a bar per indicator. It runs on a schedule with the gear you choose, and records "insufficient data" when too little is written. - [From a channel message to a merged pull request](https://cloud.usevenom.dev/docs/cloud/chat-work.md): Ask a service agent in a Venom Chat channel to build something. The request becomes a Tasks issue handed to the agent, and the thread shows its progress, its pull request with the diff, and the merge. - [Venom Support](https://cloud.usevenom.dev/docs/cloud/support.md): One shared inbox for customer email and form requests in Venom Cloud. Assign, snooze, tag and close conversations, write internal notes with @mentions, use saved replies, draft replies from your notes, and optionally let fully covered drafts send themselves after a review delay. - [Support email, in and out](https://cloud.usevenom.dev/docs/cloud/support-email.md): Point your own email provider's inbound webhook at Venom Support and connect your own SMTP server or Postmark, SendGrid, Mailgun or Resend key for replies. Venom sends nothing through any account of its own. - [Support SLA policies and reports](https://cloud.usevenom.dev/docs/cloud/support-sla.md): Set first-reply and resolution targets per priority, channel, tag or customer company, count them in business hours, pause them while snoozed, get breach alerts, and read response times, breach rate, volume, agent load and ratings on the Reports page or over MCP and REST. - [Support chat widget and help center](https://cloud.usevenom.dev/docs/cloud/support-widget.md): Put a chat on your own site that opens conversations in the Support inbox, answer them live, and publish a help center from your published Notes pages. Served from your own cloud, with no third-party script, font or analytics. - [Venom Cloud APIs overview](https://cloud.usevenom.dev/docs/cloud/api-overview.md): The four HTTP surfaces of Venom Cloud, the credentials each takes, the error shape, rate limits, request headers and where every route is documented. - [Inference API](https://cloud.usevenom.dev/docs/cloud/api-inference.md): Call models through Venom Cloud with any OpenAI SDK, stream answers, run background responses, list models, resume a dropped stream and route mesh-aware clients to a daemon. - [Voice API on Venom Cloud](https://cloud.usevenom.dev/docs/cloud/api-voice.md): Text to speech, voice lists and transcription on Venom Cloud through your own provider keys, with the orchestrator's OpenAI-shaped audio API. - [Venom Search](https://cloud.usevenom.dev/docs/cloud/search.md): Turn on Venom Search, your org's own metasearch over official APIs and open data, and call it from the API, MCP or the CLI's web_search. - [Agent and CLI API](https://cloud.usevenom.dev/docs/cloud/api-agent.md): The /v1 routes an agent or the venom CLI calls besides inference - org gears, usage, signed policy, guardrails, fleet, onboarding, backups and the session and task reports. - [Sessions API](https://cloud.usevenom.dev/docs/cloud/api-sessions.md): Share a session's trace, stream a live session to teammates, hand a session to someone else, and run venom serve sessions on a daemon through Venom Cloud. - [Knowledge and tools API](https://cloud.usevenom.dev/docs/cloud/api-knowledge.md): Read the org's memory, library and plugin marketplace with a client key, ask questions over them, and run eval, issue-intake and red-team jobs on machines you control. - [Venom for agents (one MCP server for notes, tasks and flags)](https://cloud.usevenom.dev/docs/cloud/workspace-mcp.md): Connect Claude Code, Cursor, ChatGPT or any MCP client to Venom Notes, Tasks, Flags, Forms, Incidents and Experiments through one endpoint, edit notes and issue descriptions with anchored edits, search both apps at once, and run many steps in one round trip. - [Venom Tasks API](https://cloud.usevenom.dev/docs/cloud/tasks-api.md): Read and change your org's Venom Tasks issues, teams, workflows, projects, cycles, views and inbox over the console session, and follow changes live. - [Files and pictures over MCP (Notes and People)](https://cloud.usevenom.dev/docs/cloud/mcp-files.md): How an agent puts a picture or file into Venom Notes and Venom People without base64, with a one-time upload URL or a public link, and how it sees the pictures already there. - [Venom Tasks for agents (MCP)](https://cloud.usevenom.dev/docs/cloud/tasks-mcp.md): Connect Claude Code, venom, Qoder or any MCP client to Venom Tasks, delegate issues to agents, link issues and notes, and let AI triage suggest a team, labels, a priority and duplicates. - [What agents can do in Venom (MCP parity)](https://cloud.usevenom.dev/docs/cloud/agents-capabilities.md): For every Venom app, the actions an agent can take over MCP, the ones left to a person on purpose, and the tools still coming. - [Venom Flags SDK and REST API](https://cloud.usevenom.dev/docs/cloud/flags-sdk.md): Evaluate Venom Flags in your own code with the TypeScript, Python or Go SDK or the client-side endpoint, report where flags are used from CI, and read and change flags, segments and environments over the REST API with curl. - [What agents connect to by default](https://cloud.usevenom.dev/docs/cloud/agent-defaults.md): A logged-in venom connects every Venom product's MCP server (Notes, Tasks, People, Funnel and the rest) with deferred tools; how to narrow or turn them off, and the credential sessions Venom Cloud starts get. - [Venom Experiments](https://cloud.usevenom.dev/docs/cloud/experiments.md): A/B tests on Venom Flags flags with sound statistics (CUPED, always-valid sequential results, sample ratio checks, guardrails), run by people or agents, with a decision note left in Notes. - [Sending events to Venom Experiments](https://cloud.usevenom.dev/docs/cloud/experiments-events.md): Track product events from your own app with the Flags SDK's track(), what the ingest endpoint accepts, its limits and retention, and how exposures are recorded. - [How Notes learns](https://cloud.usevenom.dev/docs/cloud/globe-learning.md): What Venom Notes adds to your vault on its own, where it gets it from, how you review it in the Inbox, and how its spending is capped. - [Insights and dashboards](https://cloud.usevenom.dev/docs/cloud/experiments-insights.md): Trends, funnels and retention over the events your apps send to Venom Experiments, saved as insights and embedded in Notes pages as live dashboards that people and agents can read. - [Admin API: orgs, members and keys](https://cloud.usevenom.dev/docs/cloud/api-admin-access.md): Script your Venom Cloud org over /api/admin/v1 — orgs, key groups, members, client keys, join tokens, CLI logins, single sign-on, org settings, signed key group policies and onboarding paths. - [Admin API: providers, gears and routing](https://cloud.usevenom.dev/docs/cloud/api-admin-routing.md): Manage an org's provider keys, gears, routing policy, venom-auto tiers, prices, model lifecycle, gear and prompt experiments, shadow tests, guardrails and prompt filters over /api/admin/v1. - [Admin API: usage, budgets and spend](https://cloud.usevenom.dev/docs/cloud/api-admin-spend.md): Read your org's usage and costs, set spend guards and alerts, forecast the month, find savings, produce chargeback statements and reconcile provider invoices over /api/admin/v1. - [Admin API: daemons, fleet and reliability](https://cloud.usevenom.dev/docs/cloud/api-admin-fleet.md): Manage your org's daemons, public nodes, GPU autoscaling, prewarming, GPU grants between key groups, failover drills, model quality checks, SLAs and the public status page over /api/admin/v1. - [Admin API: logs, audit and alerts](https://cloud.usevenom.dev/docs/cloud/api-admin-observability.md): Read the request log, run log queries, export requests and the audit log, set alerts and org webhooks, take backups and compliance packs, and manage shared, live and handed-off sessions over /api/admin/v1. - [Admin API: knowledge, tools and integrations](https://cloud.usevenom.dev/docs/cloud/api-admin-content.md): Manage an org's library, memory, marketplace, starter packs, evals, red-team runs, Slack, Linear and Jira integrations and the knowledge Ask box over /api/admin/v1. - [Admin API: customers and MSP](https://cloud.usevenom.dev/docs/cloud/api-admin-msp.md): Resell Venom Cloud to your own customers with per-customer keys, limits, prices, budgets, invoices and a branded usage portal, or manage client orgs as a managed service provider, over /api/admin/v1. - [SCIM API](https://cloud.usevenom.dev/docs/cloud/api-scim.md): Provision and deprovision your org's members from Okta, Entra ID or any SCIM 2.0 client through /scim/v2, with group-to-role mapping. - [Venom Notes API](https://cloud.usevenom.dev/docs/cloud/globe-api.md): Read and write the notes in a Venom Notes vault, follow [[wikilinks]] and backlinks, search, fetch the graph, and move a vault in and out as a zip of Obsidian-compatible markdown. - [Databases in Notes](https://cloud.usevenom.dev/docs/cloud/globe-databases.md): Notion-style databases in Venom Notes that stay plain markdown, with property types, views, filters, formulas and rollups, and an Obsidian Bases file on export. - [Log queries over the admin API](https://cloud.usevenom.dev/docs/cloud/api-log-query.md): Run, page, facet and save request-log queries from scripts through /api/admin/v1/logs; the query language itself is on the console's log query page. - [Sign-in flows](https://cloud.usevenom.dev/docs/cloud/api-auth-flows.md): Get a Venom Cloud client key for a CLI or device without pasting one (the device login), and the browser sign-in routes for GitHub, Clerk and single sign-on. - [Incoming webhooks](https://cloud.usevenom.dev/docs/cloud/api-webhooks.md): The webhook URLs Venom Cloud receives from Slack, Linear, Jira, Stripe and Clerk, how each is signed and what it answers, so you can connect and debug them. - [Public and auditor endpoints](https://cloud.usevenom.dev/docs/cloud/api-public.md): The Venom Cloud endpoints that need no Venom key (health, downloads, the docs as markdown and llms.txt) and the auditor API that checks public-mesh daemons. ## Venom Notes - [Venom Notes](https://cloud.usevenom.dev/docs/globe.md): What Venom Notes is, where it lives, who can open it, and how its screen is laid out. - [Notes, links and history](https://cloud.usevenom.dev/docs/globe/notes.md): Write notes in markdown, link them with [[wikilinks]], see what links back, and restore an earlier version. - [Page options, trash and favorites](https://cloud.usevenom.dev/docs/globe/pages.md): Give a note an icon and a cover, set its font and width, lock it, export it, bring back a deleted note, and keep favorites and recent notes above the tree. - [Share a note and publish it to the web](https://cloud.usevenom.dev/docs/globe/share.md): Invite people in your org to read one note, and publish a note as a read-only public page that search engines skip by default. - [The graph](https://cloud.usevenom.dev/docs/globe/graph.md): Read the graph view, filter it, find a note in it, and what Notes draws it with. - [How Ask finds notes](https://cloud.usevenom.dev/docs/globe/ask.md): How Ask in Notes and globe_note_related find notes by keywords, by meaning and by links, what needs an embedding model, how to run one on your own machine, and how well it works. - [Vaults, import and export](https://cloud.usevenom.dev/docs/globe/vaults.md): Switch between your personal, team and organisation vaults, start from sample notes, import an Obsidian vault and export one. - [Move notes between vaults](https://cloud.usevenom.dev/docs/globe/move-between-vaults.md): Move one note, a selection or a folder from one vault to another, with links, files and databases kept working, a clear warning about who can read them, and Undo. - [Import from Notion, Lark, Google Docs, Confluence and Evernote](https://cloud.usevenom.dev/docs/globe/import-from-apps.md): Move a whole Notion workspace into Notes with an integration token, or bring a Notion export, Lark or Google docs, Word files, a Confluence space, Evernote notebooks or a folder of markdown, with nesting and links kept and a preview before anything is written. - [Sync a folder with venom globe sync](https://cloud.usevenom.dev/docs/globe/sync.md): Keep a local folder of markdown, such as an Obsidian vault, and a Venom Notes vault in step both ways. Edits on both sides are merged three ways, overlapping edits keep both copies, and deletes only go to a trash. - [Import from ChatGPT and Claude](https://cloud.usevenom.dev/docs/globe/import-from-ai.md): Bring what you have told ChatGPT and Claude into Notes from your own data export, or paste what your AI remembers, and review every suggestion before it reaches your vault. ## Venom Incidents - [Venom Incidents](https://cloud.usevenom.dev/docs/incidents.md): 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. - [Errors](https://cloud.usevenom.dev/docs/incidents/errors.md): Triage your apps' errors: the issue stream and its keys, the issue page, states and regressions, merging, source maps and filing a Tasks issue. - [Incidents](https://cloud.usevenom.dev/docs/incidents/incidents.md): Declare an incident with a severity and roles, follow a timeline that fills itself with flag changes, releases and alerts, and post status updates that reach your status page. - [The loop](https://cloud.usevenom.dev/docs/incidents/the-loop.md): An error spike opens an incident, Venom ranks what changed, rolls back the flag that did it through Venom Flags (if you allow it), and files a Tasks issue for an agent with the stack and the suspects. - [Postmortems](https://cloud.usevenom.dev/docs/incidents/postmortems.md): A blameless postmortem draft in Notes for every resolved incident, its action items as Tasks issues, an eval case from the regression, and a draft PR with a failing test. - [Error alerts](https://cloud.usevenom.dev/docs/incidents/alerts.md): Rules that tell you about a new issue, a regression, a spike, a threshold or a burning error budget: the bell, org webhooks and Slack, a dry run over the last 24 hours, and how a hit is decided. - [On-call](https://cloud.usevenom.dev/docs/incidents/on-call.md): Schedules with layered rotations and overrides, escalation policies, and pages that tell the right person through the bell, a webhook, Slack, SMS and a phone call, and escalate until someone acknowledges. - [Alert sources](https://cloud.usevenom.dev/docs/incidents/alert-sources.md): Point Prometheus Alertmanager, Grafana or any JSON sender at a signed URL to page the on-call and, if you want, open an incident. - [The errors SDK and ingest](https://cloud.usevenom.dev/docs/incidents/errors-sdk.md): Send your app's errors to your Venom Cloud with the dependency-free TypeScript SDK or plain HTTP: init, captureException, breadcrumbs, flags served, releases, grouping and the limits. - [Migrate from Sentry, or send OpenTelemetry exceptions](https://cloud.usevenom.dev/docs/incidents/migrate-from-sentry.md): Keep your Sentry SDKs and point the DSN at your own Venom Cloud, or export OpenTelemetry exception events with a collector: the DSN, the key, what is kept and what is dropped. ## Venom Comms - [Venom Comms](https://cloud.usevenom.dev/docs/comms.md): 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. - [The Comms API](https://cloud.usevenom.dev/docs/comms/api.md): Send messages and place calls with /v1/comms and an org API key; read conversations and events; manage opt-outs; and the comms_* MCP tools for agents. - [Comms providers](https://cloud.usevenom.dev/docs/comms/providers.md): Connect your Sinch account step by step, your own Jasmin or Kannel SMS gateway or a Telegram bot, or try Comms with the fake provider; how callbacks are verified and how fallback works. - [WhatsApp through Meta's Cloud API](https://cloud.usevenom.dev/docs/comms/whatsapp-meta.md): Connect your WhatsApp Business number straight to Meta's Cloud API: paste three values and Venom sets up the webhooks, templates and the Support inbox itself. What Meta requires, what it costs, keeping the number on the WhatsApp Business app, and what agents can do. - [Keep your number on the WhatsApp Business app (coexistence)](https://cloud.usevenom.dev/docs/comms/whatsapp-coexistence.md): Connect with Meta keeps your WhatsApp Business app number on your phone and brings the same chats into Venom: what Meta changes in the app first, what you do on the phone, the 24-hour history and contacts sync, messages you send from the phone, and how to disconnect. - [Email from your own mailbox](https://cloud.usevenom.dev/docs/comms/email.md): Connect a mailbox with an app password so Comms and Outreach send email from you. Venom checks the sign-in and the domain's SPF, DKIM and DMARC, paces sends, reads only reply and bounce headers, and puts a one-click unsubscribe in every email. - [Telegram from your own account](https://cloud.usevenom.dev/docs/comms/telegram-personal.md): Send your approved Outreach messages from your own Telegram account through the Venom daemon on your computer. You log in there, Venom Cloud never holds the login, and the daemon keeps the account under Telegram's limits. - [Comms profiles](https://cloud.usevenom.dev/docs/comms/profiles.md): Routing with fallback for messages and calls: the built-in page, support and notify profiles, your own chains, acknowledgements, and which profiles agents may use. - [Comms compliance](https://cloud.usevenom.dev/docs/comms/compliance.md): What Venom Comms enforces for you (STOP and opt-outs, quiet hours in the recipient's time zone, sender-id rules per country, WhatsApp's 24-hour window) and what stays your responsibility. - [Incidents paging by SMS and phone](https://cloud.usevenom.dev/docs/comms/incidents-paging.md): On-call pages that text each member, call them a few minutes later unless someone acknowledged, read the alert in your org's voice, and take 1 to acknowledge or 2 to escalate. - [Messaging channels in Support and People](https://cloud.usevenom.dev/docs/comms/support-and-people.md): Customers write on WhatsApp, SMS, RCS or Telegram and the conversation lands in Support; you capture people by texting a number or a bot. Routing, the WhatsApp 24-hour window and templates, delivery ticks, files, and what stays private. - [Venom Line, an AI voice agent on your number](https://cloud.usevenom.dev/docs/comms/venom-line.md): Let an AI agent answer live calls on your org's number: set up the media bridge on your own orchestrator, pick the agent's knowledge, tools and voice, run local speech models, and see each call's transcript, ticket and latency afterwards. ## Venom Funnel guides - [Venom Funnel guides](https://cloud.usevenom.dev/docs/funnel.md): Guides for the parts of Venom Funnel that go beyond the pipeline board, starting with Outreach, personalised follow-up sequences. - [Outreach](https://cloud.usevenom.dev/docs/funnel/outreach.md): Personalised follow-up sequences in Funnel. Each message is written only from what Venom knows about the person, sent by email or WhatsApp Business or handed to you to send from your own phone, and stopped the moment they reply. ## Venom Calendar - [Venom Calendar](https://cloud.usevenom.dev/docs/calendar.md): 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. - [How Calendar works](https://cloud.usevenom.dev/docs/calendar/overview.md): What Venom Calendar does, how it compares with Calendly and Google appointment schedules, how bookable times are computed, and the safety and privacy rules it keeps. - [.ics feeds](https://cloud.usevenom.dev/docs/calendar/ics-feeds.md): Paste any calendar's .ics address so its busy time blocks your booking slots and its meetings reach Venom People: where to find the address in Google, Outlook, iCloud and TripIt, how fresh the data is, and how the address is kept. - [Google accounts](https://cloud.usevenom.dev/docs/calendar/google.md): Connect as many Gmail and Google Workspace accounts as you like, pick which calendars block time, keep busy time fresh within a minute, bring your own OAuth client, and see exactly what Venom reads and stores. - [The Calendar app](https://cloud.usevenom.dev/docs/calendar/app.md): Venom Calendar at /calendar: every connected calendar in one week view, connections and their rules, your hours, event types with a live preview, bookings, your profile, and the keyboard. - [Microsoft accounts](https://cloud.usevenom.dev/docs/calendar/microsoft.md): Connect Microsoft 365 work accounts and Outlook.com personal accounts, as many as you like, keep their busy time fresh, write bookings with a Teams link, and bring your own Entra app. - [Booking pages](https://cloud.usevenom.dev/docs/calendar/booking-pages.md): Your /meet page: event types, times that are really free, holds while someone fills the form, single-use and one-off links, manual confirmation, the invitee's reschedule and cancel link, and the API and MCP tools behind it. - [Integrations with People, Funnel, Outreach, Tasks and Notes](https://cloud.usevenom.dev/docs/calendar/integrations.md): What a booking does in the rest of Venom: the invitee becomes a contact with the meeting logged, the deal moves, Outreach stops, a follow-up task and a meeting note wait for you, and a link tied to a person fills the form in. - [Invites and reminders](https://cloud.usevenom.dev/docs/calendar/reminders.md): What a booking sends: a calendar invite to the invitee, you and your other accounts, reminders by email, SMS, WhatsApp or Telegram, a reconfirmation, a thank-you, and the no-show button. - [Teams, routing forms and polls](https://cloud.usevenom.dev/docs/calendar/teams.md): Event types hosted by several people: collective (everyone attends) or round robin (one host per booking, fairly). Routing forms that book on submit, and group polls to find a time. - [Embedding a booking page](https://cloud.usevenom.dev/docs/calendar/embed.md): Put a booking page on your own site, inline or as a popup, with one script from your own cloud: prefill the name and email, pass utm_* parameters, and hear when someone books. - [Agents schedule for you](https://cloud.usevenom.dev/docs/calendar/agents.md): Ask venom, Chat or Claude to find time with someone: it finds real free times, holds them, sends the options in their time zone with a one-tap link, and books the one they pick. The same Share availability works by hand from the week view. ## Venom Computers - [Venom Computers](https://cloud.usevenom.dev/docs/computers.md): 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. - [Agents on computers](https://cloud.usevenom.dev/docs/computers/agents-on-computers.md): Give a Chat agent or a Tasks agent a computer. Its mentions and delegations then run on its own browser on your daemon, ask you before risky actions, call you in for a login or a CAPTCHA, and stop at their daily limit. - [What a computer is](https://cloud.usevenom.dev/docs/computers/overview.md): A computer is one agent's persistent browser on one of your daemons. How it is placed, started and stopped, who can see and control it, and what the cloud keeps about it. - [Enable Computers on a daemon](https://cloud.usevenom.dev/docs/computers/enable.md): One click turns Venom Computers on for a daemon, from the Computers app, the daemon page or the daemon's own dashboard. What it checks, how long it takes, what the error messages mean, and the MCP tools and REST routes behind it. - [Run Computers on your own daemon](https://cloud.usevenom.dev/docs/computers/self-host.md): What a daemon needs to host Venom Computers: Docker, RAM and disk sizing from the measured numbers, the venom-computer image (published and digest-pinned, or built locally), the compose profile, a reachable endpoint for the live view, Chromium updates, and Kubernetes. - [The Computers app](https://cloud.usevenom.dev/docs/computers/console.md): Watch every agent's computer in one fleet view, open a live view, take control for a login or a CAPTCHA and hand it back, and choose whether a computer is dedicated to one agent or shared by several. - [Computers for agents](https://cloud.usevenom.dev/docs/computers/agents.md): The computers_* MCP tools and the REST API behind them, who a call acts as, and what an agent may do with its own computer and the shared ones it belongs to. - [Routines](https://cloud.usevenom.dev/docs/computers/routines.md): Run a Chat or Tasks agent, or one of your bots, on a schedule, when an email arrives or when a webhook is called, and keep every run with its status, cost and result. - [Desktop computers](https://cloud.usevenom.dev/docs/computers/desktop.md): A computer that is a full Linux desktop instead of a browser alone, with a terminal, a file manager and any app in the image. What it costs, how to run one, and what an agent can do on it. - [Capacity and sizing](https://cloud.usevenom.dev/docs/computers/capacity.md): What one daemon holds, measured with the Computers load test. Memory per active browser, how many run at once, resume time, tool-call overhead, burst behaviour, and how to run the test on your own machine. - [Saved logins and cards](https://cloud.usevenom.dev/docs/computers/saved-logins.md): Save a login, a card or a text once, and an agent types it into pages on its computer without ever seeing it. Where values are stored, which pages may receive them, and how to revoke. - [Sharing a computer](https://cloud.usevenom.dev/docs/computers/sharing.md): Let several agents use one browser so a site is logged into once, with turns on a shared tab, using WhatsApp Web as the example. - [Watch a computer and take control](https://cloud.usevenom.dev/docs/computers/watch-and-control.md): How Watch and Take control reach a computer with nothing to set up (WebRTC straight to the daemon, even behind NAT), what the STUN server sees, when a TURN server is needed (yours or a managed one), the direct and snapshot fallbacks, the control lease, and how an agent asks for a person. ## Venom Agents - [Venom Agents](https://cloud.usevenom.dev/docs/agents.md): Chats with coding agents on your own repositories and with agents on your computers, run on your own daemons and reached from the cloud. - [Get started with Venom Agents](https://cloud.usevenom.dev/docs/agents/getting-started.md): From a connected daemon to your first agent chat: open /agents, pick a new project, a scratch folder or a folder already on the machine, and send a prompt. Nothing to set up on the daemon. - [The Agents app](https://cloud.usevenom.dev/docs/agents/app.md): Start a chat with a coding agent on one of your projects or with an agent on one of your computers, follow it as it works, answer its approvals and read its diffs, from any browser or phone, and install it as an app that notifies you. - [Quick chats](https://cloud.usevenom.dev/docs/agents/quick-chat.md): Chat with an agent that needs no computer, daemon or sandbox. It works through MCP servers only, Venom Notes by default, with the other Venom servers and the catalog servers you connected a switch away. - [Where a daemon chat's model runs](https://cloud.usevenom.dev/docs/agents/model-source.md): Run a code or computer chat's model on the daemon's own keys or on your organisation's cloud keys, see which one each gear uses, and set or lock the default for your organisation. - [Computer chats](https://cloud.usevenom.dev/docs/agents/computer-chats.md): Chat with an agent that works in one of your Venom Computers, watch its live screen beside the conversation, and answer the browser's asks in the chat. - [Files and pictures in a chat](https://cloud.usevenom.dev/docs/agents/attachments.md): Attach pictures, Word documents and text or code files to a quick chat's message (or a chat with a bot), by picking, pasting or dropping them, and the agent reads them. - [Bots](https://cloud.usevenom.dev/docs/agents/bots.md): Named agents with an avatar and your own standing instructions. Chat with one any time, or let it run on a schedule, an email, a webhook or when something happens in your workspace, and read what it did when you are back. - [Bots that reach out](https://cloud.usevenom.dev/docs/agents/bot-outreach.md): Let a bot write to your people while you sleep, as drafts you check in the morning, sent for you through Venom Comms, or sent from your own WhatsApp Web or LinkedIn on the bot's own computer, inside limits you set. It can also keep your People records filled in. - [Chats API and MCP tools](https://cloud.usevenom.dev/docs/agents/api.md): The routes under /api/workspace/agents, the live event stream, and the agents_* MCP tools with their REST twins under /api/v1/agents. - [The bot register for admins](https://cloud.usevenom.dev/docs/agents/bot-register.md): See every bot in your organisation, who owns it and what it may do, on one read-only page for owners and admins. Its instructions, memory and messages stay private to its owner. - [Plans and the add-on](https://cloud.usevenom.dev/docs/agents/plans.md): Venom Agents is included in Team and up; what a team without it sees in the app, the API and the MCP tools, how usage is booked, and what an operator sets. ## Venom Studio - [Venom Studio](https://cloud.usevenom.dev/docs/studio.md): 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. - [What Studio makes](https://cloud.usevenom.dev/docs/studio/overview.md): The three kinds of artifact (deck, page, HTML page), who owns and sees them, the limits, and where Studio keeps what you make. - [The Studio pages](https://cloud.usevenom.dev/docs/studio/console.md): The list with previews, the viewer, the light editor with a live preview, present mode, print, the share dialog, version history and theme settings, and how to reach Studio from the rail, ⌘K and Home. - [Blocks and charts](https://cloud.usevenom.dev/docs/studio/blocks.md): Every block a page or slide can hold, with a spec for each text, table, chart and diagram block, and how Venom checks a spec. - [Charts, tables and KPI components](https://cloud.usevenom.dev/docs/studio/components.md): The data components an agent fills with numbers instead of drawing anything, the one data contract they share, the shapes Venom also reads, and how to place them in a page, a deck slide or an html page. - [Slide layouts and themes](https://cloud.usevenom.dev/docs/studio/layouts-and-themes.md): The thirteen slide layouts and their slots, the built-in themes, how to set your organisation's own colours, fonts, logo and corner radius once, one artifact's own tweaks, and themed HTML pages. - [Header, footer and marks](https://cloud.usevenom.dev/docs/studio/marks.md): Put your company, logo, author, date, a confidentiality label, a header, a footer and slide numbers on decks, pages and html pages, on screen, in print and in PowerPoint, with organisation defaults each artifact can override. - [Edit by id](https://cloud.usevenom.dev/docs/studio/edits.md): Change one slide or block without resending the artifact, in batches that apply all or none, with a version for every write and a check that stops two writers overwriting each other. - [Share, present and print](https://cloud.usevenom.dev/docs/studio/sharing.md): Who can see an artifact, public share links you can revoke, present mode with notes, printing to PDF, PowerPoint downloads, and why a free-form HTML page runs sandboxed. - [Research runs](https://cloud.usevenom.dev/docs/studio/research.md): How Studio researches and writes a report on the server — plan with goals, parallel researchers over Venom Search, scholarly works and World Bank data, an analysis per section, the build and a review — with the intensity and agent controls, budgets, and what happens when research is off. - [Studio for agents](https://cloud.usevenom.dev/docs/studio/agents.md): The studio_* MCP tools and the REST API, the cheap workflow that keeps an agent's token use small, and what each answer returns. ## Mesh - [Mesh](https://cloud.usevenom.dev/docs/mesh.md): 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. - [How the private mesh works](https://cloud.usevenom.dev/docs/mesh/cloud-mesh.md): How Venom Cloud routes a key group's requests to its own daemons, directly with a 307 and a ticket or relayed through the cloud, and what each side sees, signs and keeps. - [Connect a daemon](https://cloud.usevenom.dev/docs/mesh/connect-daemon.md): Put a machine on your org's Venom Cloud mesh with a join token, from the desktop daemon's dashboard, make daemon, or the orchestrator binary, and set its endpoints, location and limits. - [The public mesh](https://cloud.usevenom.dev/docs/mesh/public-mesh.md): Host a public node that serves strangers' requests, or route your requests to public nodes, and how signed receipts, sampled audits, canaries and witnessed QoS keep nodes honest. - [Provenance and receipts](https://cloud.usevenom.dev/docs/mesh/provenance.md): The two kinds of signed receipt venom produces, for a completion a public node served and for a commit an agent made, what each proves, and how to check them yourself. - [Daemon API reference](https://cloud.usevenom.dev/docs/mesh/daemon-api.md): Every route a daemon calls on Venom Cloud under /api/mesh/v1, with its authentication, request and response bodies, and errors. ## Deploy - [Deploy](https://cloud.usevenom.dev/docs/deploy.md): 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. - [Docker Compose and profiles](https://cloud.usevenom.dev/docs/deploy/compose.md): Run the orchestrator and console with docker compose from a venom checkout, add local inference, metrics or web search with profiles, and share a GPU box with make daemon. - [The web console](https://cloud.usevenom.dev/docs/deploy/console.md): Configure the venom web console's login, reverse-proxy trust, connection to the orchestrator and venom serve, and the data files behind its Flow and Scorecards pages. - [Observability with Prometheus and Grafana](https://cloud.usevenom.dev/docs/deploy/observability.md): Run Prometheus and a provisioned Grafana dashboard next to the orchestrator with the observability compose profile, or scrape the orchestrator's /metrics from your own monitoring. - [Kubernetes](https://cloud.usevenom.dev/docs/deploy/kubernetes.md): Run the orchestrator on Kubernetes from venom's kustomize manifests, with keys in Secrets and the config as a generated ConfigMap, optionally as a Venom Cloud daemon. - [Helm chart for Kubernetes](https://cloud.usevenom.dev/docs/deploy/kubernetes-helm.md): Install Venom Cloud and the orchestrator on an existing Kubernetes cluster with one Helm chart, your own or a bundled Postgres, generated secrets, a pre-upgrade migration Job, ingress with TLS and optional NetworkPolicies. - [Self-host Venom Cloud](https://cloud.usevenom.dev/docs/deploy/self-host-cloud.md): Run the Venom Cloud workspace on your own server with Docker Compose, your own Postgres and a built-in cron runner, with no Vercel or Neon. - [Install Venom Cloud on a Linux server](https://cloud.usevenom.dev/docs/deploy/install-server.md): One command that checks your server, generates the secrets, starts Venom Cloud with HTTPS (on one server, or with your own database server and daily backups) and leaves a venom-cloud command for status, logs, backups, restores and upgrades. - [Deploy Venom Cloud on AWS](https://cloud.usevenom.dev/docs/deploy/aws.md): Create one CloudFormation stack in your own AWS account. Standard is one encrypted EC2 instance with HTTPS and nightly snapshots; Production is an Auto Scaling group behind a load balancer, RDS Postgres with pgvector, Secrets Manager and an S3 bucket for backups. - [Install Venom Cloud on a Mac](https://cloud.usevenom.dev/docs/deploy/install-mac.md): Run Venom Cloud on your own Mac from the command line, at http://localhost:8080, in Docker Desktop, OrbStack or Colima, with no root, started again at each login by a LaunchAgent. - [Update a self-hosted Venom Cloud](https://cloud.usevenom.dev/docs/deploy/updates.md): Check for a signed release, upgrade with a preflight, a database backup, a health check and automatic rollback, roll back from the console or by hand, switch on automatic updates in a maintenance window, use the preview channel, and upgrade an air-gapped server from an offline bundle. - [Back up a self-hosted Venom Cloud](https://cloud.usevenom.dev/docs/deploy/server-backups.md): Scheduled backups of the database and the server's files to its own disk or your S3-compatible bucket, a verify restore into a scratch database, and a full export to download, all from Settings, Server backups. - [Link a self-hosted install to Venom for managed service](https://cloud.usevenom.dev/docs/deploy/management-link.md): Connect a self-hosted Venom Cloud to Venom's management plane with a one-time code, read exactly what its hourly heartbeat sends, disconnect at any time, and how Venom's operators see linked installs. - [The desktop daemon](https://cloud.usevenom.dev/docs/deploy/desktop-daemon.md): Install venom-daemon on a desktop or GPU box with no Docker, manage it from the command line, the dashboard or the macOS menu bar, connect it to Venom Cloud, and turn on opt-in auto-update. - [Projects on the desktop daemon](https://cloud.usevenom.dev/docs/deploy/projects.md): The folders on your computer that coding agents can work in, from the daemon's dashboard or with venom-daemon projects; the workspaces Venom Cloud makes for chats; nothing else is served. - [Set up "Connect with Meta" for WhatsApp](https://cloud.usevenom.dev/docs/deploy/meta-app.md): Everything the operator does in Meta's developer console so Settings, Comms offers Connect with Meta (WhatsApp Embedded Signup and coexistence): the app, Tech Provider, app review, the login configuration, domains, the webhook and four environment variables. - [Terraform BYOD GPU](https://cloud.usevenom.dev/docs/deploy/byod-gpu.md): Rent a GPU box on RunPod or Lambda Cloud with venom's Terraform module, install the released venom-daemon with Ollama and your models on it, and join it to Venom Cloud. - [Air-gapped install](https://cloud.usevenom.dev/docs/deploy/airgap.md): Build one verified archive of venom on a connected machine with make airgap, carry it to a machine with no network, install it with checksum and signature checks, and bring your own model. - [Releases and signatures](https://cloud.usevenom.dev/docs/deploy/releases.md): Verify a venom download against SHA256SUMS and its minisign signature, and build your own release, library packages, SBOM and other artifacts from a checkout with make release, make libs and related targets. - [The venom-computer host image](https://cloud.usevenom.dev/docs/deploy/computer-host.md): Build and run the host container for Venom Computers, with venom-seatd, the seat endpoints, the environment it reads, how to run it locked down, and what a seat costs in memory. - [Venom Computers on a daemon](https://cloud.usevenom.dev/docs/deploy/computers.md): Turn on persistent agent browsers on your own daemon, and see how many seats it holds, how many run at once, what happens beyond that, how idle seats hibernate, and what the daemon tells the cloud. ## Evals - [Evals](https://cloud.usevenom.dev/docs/evals.md): 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. - [Running evals](https://cloud.usevenom.dev/docs/evals/running.md): Run the eval suite with make eval against an orchestrator or any OpenAI-compatible server, pick tasks with --filter, read pass@1 and pass^k, and keep spend under --max-usd with a dry run first. - [Comparing runs and the regression gate](https://cloud.usevenom.dev/docs/evals/compare.md): Decide whether a harness or model change regressed with make eval-compare against the committed baseline, get a capped verdict for a branch with make eval-verdict, rank gears by cost, and mine eval tasks from your own repository with make eval-mine. - [Eval tools and probes](https://cloud.usevenom.dev/docs/evals/tools-and-probes.md): Pin the language servers and formatters every eval trial uses with make eval-tools, check which reasoning efforts each provider really accepts with make effort-probe, and list MCP Registry servers for the cloud catalog with make mcp-catalog-sync. - [Cloud eval runner](https://cloud.usevenom.dev/docs/evals/cloud-runner.md): Run the evals your team queues in Venom Cloud on a machine you control with venom eval run --cloud, with a spend cap per run and no provider keys handed to the trials. - [Venom next to pi on the Harness Leaderboard setup](https://cloud.usevenom.dev/docs/evals/harness-leaderboard.md): Run venom and stock pi side by side on the Harness Leaderboard's DeepSWE setup through Harbor, one model at one effort, with a spend cap and a dry run first. - [Fine-tuning on your own sessions](https://cloud.usevenom.dev/docs/evals/finetune.md): Turn your good venom sessions into a redacted fine-tuning dataset with venom finetune export and train a local LoRA with venom finetune train or make finetune. Off by default, nothing is uploaded. ## Reference - [Reference](https://cloud.usevenom.dev/docs/reference.md): 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. - [Environment variables](https://cloud.usevenom.dev/docs/reference/environment.md): Every environment variable the venom CLI, the harness and the dev stack read, with what it does and its default. - [Architecture, ports and contracts](https://cloud.usevenom.dev/docs/reference/architecture.md): How venom's pieces fit together, which port each one listens on, and which file is the contract between them. - [Error codes](https://cloud.usevenom.dev/docs/reference/errors.md): The error shapes and codes of the orchestrator, Venom Cloud, venom serve and the CLI, with what each means and whether a retry can help. - [x-venom headers](https://cloud.usevenom.dev/docs/reference/headers.md): Every x-venom-* HTTP header venom sends or answers with, on the orchestrator, Venom Cloud and venom serve, and what each one changes. - [Limits and defaults](https://cloud.usevenom.dev/docs/reference/limits.md): The built-in size caps, timeouts, queues and counts of the orchestrator, venom serve, Venom Cloud and the CLI, and where to change each one. - [Glossary](https://cloud.usevenom.dev/docs/reference/glossary.md): Short definitions of the words venom's docs, config and APIs use, from alias and gear to daemon, relay and lease. - [Design decisions (ADRs)](https://cloud.usevenom.dev/docs/reference/adr.md): One line per architecture decision record, saying what venom decided and why it matters to you. - [make targets](https://cloud.usevenom.dev/docs/reference/make-targets.md): What each make target in a venom checkout does, for running the dev stack, building and testing. - [Audit and compliance export](https://cloud.usevenom.dev/docs/reference/audit-export.md): Export one period's evidence of who approved what with venom audit export, and check it offline with venom audit verify-export. - [Single sign-on and SCIM for Venom Cloud](https://cloud.usevenom.dev/docs/reference/cloud-sso.md): Connect a Venom Cloud organisation to Okta, Microsoft Entra ID or Google Workspace over OIDC or SAML, and let SCIM keep the member list in step. - [Reasoning-effort auto-tuning](https://cloud.usevenom.dev/docs/reference/effort-auto-tuning.md): Let the orchestrator pick a reasoning effort per request with reasoning_effort auto in a route profile, and what it will never override. - [Evidence bundles](https://cloud.usevenom.dev/docs/reference/evidence-bundle.md): Print the proof a change carries with venom evidence, as JSON or a pull request comment, and build it from code with @venom/harness/evidence. - [Headless output with --json](https://cloud.usevenom.dev/docs/reference/headless.md): Drive venom commands from CI, editors and other agents with --json, which prints one JSON document on stdout per command. - [Intent ledger](https://cloud.usevenom.dev/docs/reference/intents.md): Record what is wanted as an intent with goals, constraints and acceptance checks, and let agents claim it, attach evidence and close it with venom intent. - [Knowledge Q&A](https://cloud.usevenom.dev/docs/reference/knowledge-qa.md): Ask how your team works with venom ask, the console's Ask page or Slack, and get an answer cited from org memory, the team library, session summaries and your repo's docs. - [Onboarding paths](https://cloud.usevenom.dev/docs/reference/onboarding.md): Build guided first tasks for new members on Venom Cloud, and walk them with venom onboard. - [Public mesh hardening](https://cloud.usevenom.dev/docs/reference/public-mesh-hardening.md): How the public mesh checks that a daemon run by a stranger serves the registered model at the promised quality, what was measured, and what is still weak. - [Stacked pull requests with venom stack](https://cloud.usevenom.dev/docs/reference/stacked-prs.md): Split a large branch into a chain of small pull requests, submit, restack and land them with venom stack. - [Browser IDE](https://cloud.usevenom.dev/docs/reference/web-ide.md): Review and steer an agent session from a browser with the small IDE venom serve hosts at /v1/ide, and what it can and cannot do. - [How these docs are built](https://cloud.usevenom.dev/docs/reference/public-docs.md): Build and check the public docs from a venom checkout, serve them from your own Venom Cloud, and read them as markdown, llms.txt or search.json. - [The offline API and SDK docs site](https://cloud.usevenom.dev/docs/reference/docs-site.md): Build a static, dependency-free docs site from venom's own contracts with make docs-site, for air-gapped networks, and check it with make docs-site-check. - [Realtime voice agents (design)](https://cloud.usevenom.dev/docs/reference/voice-agents.md): The design for phone and browser voice agents on the harness, such as a receptionist or a collections agent, and where each part will run. Not built yet. - [Research behind the design](https://cloud.usevenom.dev/docs/reference/research.md): The cited research venom's design decisions rest on, how references are keyed, and the study of opencode that fed the backlog. ## Cookbook - [Cookbook](https://cloud.usevenom.dev/docs/cookbook.md): End-to-end recipes that put venom's pieces together, from an offline coding setup to a multi-tenant SaaS with a phone agent. - [Build a collections SaaS on venom](https://cloud.usevenom.dev/docs/cookbook/collections-saas.md): Put the harness, the orchestrator, guardrails, human handoff and the compliance evidence together into a multi-tenant collections product, with the phone agent's design and what of it ships today. - [Embed the harness in a Next.js app](https://cloud.usevenom.dev/docs/cookbook/nextjs-app.md): Build a Next.js 16 app that streams a venom agent's answer to the browser, then move the sessions to a venom serve worker and answer the agent's approvals from the page. - [Run venom fully offline with Ollama](https://cloud.usevenom.dev/docs/cookbook/offline-ollama.md): Run the venom coding agent on local models with no network, from Ollama alone up to the orchestrator and an air-gapped install, and check that nothing left the machine. - [Put venom behind Venom Cloud for a team](https://cloud.usevenom.dev/docs/cookbook/team-cloud.md): Give a team one Venom Cloud endpoint, a key and budget per person, provider keys or your own GPU box as a daemon, and the shared policy, then point everyone's venom at it. - [Use venom from another agent over MCP](https://cloud.usevenom.dev/docs/cookbook/mcp-from-other-agents.md): Give Claude Code, Codex, Cursor or your own agent venom's browser tools, its web search and a whole venom agent as MCP tools, and know which other interfaces fit better. - [Add a provider key and route by cost](https://cloud.usevenom.dev/docs/cookbook/cost-routing.md): Add a cloud provider to your orchestrator next to local models, make an alias that tries the cheapest target first, choose it per key, request or gear, and read back what it cost. ## API reference - [API reference](https://cloud.usevenom.dev/docs/api.md): The HTTP APIs of venom serve, the orchestrator and Venom Cloud, generated from their contracts. - [Harness server API](https://cloud.usevenom.dev/docs/api/harness-server.md): Every operation of venom serve's HTTP API (66 operations), with parameters, bodies, responses, schemas and a curl line each. - [Orchestrator API](https://cloud.usevenom.dev/docs/api/orchestrator.md): The Go orchestrator's OpenAI-compatible and admin HTTP API (78 endpoints): routes, headers, bodies and errors. - [Venom Cloud API](https://cloud.usevenom.dev/docs/api/cloud.md): Every public /v1 route of Venom Cloud (115 operations): what it does, its client-key auth and a curl line.