---
title: Venom Agents
description: Chats with coding agents on your own repositories and with agents on your computers, run on your own daemons and reached from the cloud.
section: agents
order: 0
audience: [user, operator, builder, agent]
sources: [services/nodejs-cloud/lib/agents, services/nodejs-cloud/lib/billing/addon-catalog.ts, services/nodejs-cloud/app/api/workspace/agents/chats, services/nodejs-cloud/migrations/0276_agent_chats.sql]
features: []
---

Venom Agents lets a member talk to an agent from the cloud while the agent works on the organisation's own machines. A
**chat** is one conversation with one agent:

- a **code chat** runs a coding agent (`venom serve`) on one of your daemons, in a project directory that daemon offers;
- a **computer chat** runs an agent on one of your [computers](/docs/computers.md).

Every chat is connected to the workspace's products (Notes, Tasks, People, Funnel, Support, Calendar and the rest) as
the member who started it: the agent can search a note, file a task or look up a person with nothing to set up, and only
reads and changes what that member could. The cloud gives the session a key of that member's for those tools and
revokes it when the chat is archived or ends, or the member leaves
([Sessions Venom Cloud starts](/docs/cloud/agent-defaults.md#sessions-venom-cloud-starts)).

The repository never leaves the daemon. The cloud relays your messages and the agent's events, and reads files and
diffs from the daemon when you ask for them. It stores who started each chat, where it runs, its title, model, mode and
state, and nothing the agent says.

Start and follow chats in [the Agents app](/docs/agents/app.md) at `/agents`, from any browser or phone, or through the
[API and the `agents_*` MCP tools](/docs/agents/api.md). New here? [Get started](/docs/agents/getting-started.md) adds a project folder on your
daemon and starts a first chat; [Computer chats](/docs/agents/computer-chats.md) covers agents that work in a browser.

## Who can do what

A chat belongs to the member who started it. Only they send to it, answer its approvals and archive it. Org owners and
admins can read every member's chats (`all=1`), but cannot send to them. Developers start chats; billing and viewer
members can't (the product access matrix row **Agents**, [Teams and roles](/docs/cloud/teams.md)). A computer chat also
needs the right to use that computer in Venom Computers.

## Your usage, your limits

The cloud calls the daemon with a key minted for you and this purpose (`agents`). It is never shown, so the model
calls the agent makes are booked to you: your budgets, your model access and your audit trail apply. When a member
leaves the organisation, that key is revoked and their chats stop reaching the daemons.

## Projects

A code chat runs in a directory the daemon offers: a folder its owner added, or a [workspace](/docs/agents/app.md#workspaces) made
from the cloud (a new project, empty or cloned, or a scratch folder that goes with its chat). A current desktop daemon
needs no setup for the second kind. `GET /api/workspace/agents/projects?daemon=<id>` (or `agents_project_list`) asks the
daemon for the list; `agents_workspace_create` makes a workspace. A daemon whose `venom serve` is too old to list
projects answers `501 projects_unavailable`, and one too old to make workspaces `501 workspaces_unavailable`; update the
daemon.

## The add-on

Venom Agents is an add-on like Notes and Tasks: included in Team and up. While its price is not configured
(`STRIPE_PRICE_AGENTS_SEAT` unset) every organisation has it. Without it the app shows how to add it and every route and
tool answers `403 addon_required`. [Plans and the add-on](/docs/agents/plans.md) has the details.


## In this section {#in-this-section}

- [Get started with Venom Agents](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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.
