Your agents, from any browser.The work stays on your machines.
Start a coding agent on one of your repositories, or an agent on one of your computers, from a browser or a phone. It runs on your own daemon. You watch it work, answer what it asks and read its diffs as it goes.
Included in Team and up, from $249/month.
Getting started
Three steps to your first chat
A daemon offers nothing until you add a folder, so you decide which repositories an agent can work in.
- 1
Add a project folder
On the machine that runs your daemon, add the folder that holds your code. Every git repository directly inside it shows up as a project.
venom-daemon projects add ~/code/my-app
- 2
Open Agents and pick a project
In the prompt box, choose the project, a model from your organisation's gears and how much the agent may do without asking.
- 3
Say what you want
The agent starts on your daemon and its answer streams in. Steer it while it runs, or stop it with Esc.
No daemon yet? It installs in one step. Get the Venom daemon
What you get
A clean chat with the agent's work folded in
One chat is one agent. Tool calls, approvals and file changes appear in the conversation, folded until you open them.
Code chats
A coding agent (venom serve) works in a project on your daemon, under the same permission rules as in your terminal.
- Projects grouped by daemon, with each repository's git branch
- Modes: ask before acting, accept edits, auto, or plan first
- Send to steer the turn that is running, or queue a message for after it
Computer chats
An agent works in one of your Venom Computers, and the computer's live screen sits beside the conversation.
- Watch the agent use the browser as it goes
- Take control beside the chat, with an address box to open a page
- On a phone, switch between the chat and the screen
Approvals in the stream
When the agent wants to do something your rules don't allow, the request appears in the chat as buttons.
- Allow once, allow for this chat, or deny
- Questions come with their options as buttons, or type your own answer
- A chat started from a browser always keeps its approval prompts
Diffs per turn
After a turn that changed files, open the list and then any file's diff.
- Read from your daemon when you open it, never kept in the cloud
- Secret files such as .env stay hidden, with the reason shown
- A dropped connection picks up again from the last event
Your machines, your keys
The cloud relays the chat. It does not hold your code.
Venom Cloud passes your messages to the daemon and the agent's events back to you.
Code stays on the daemon
The agent runs where the repository is. Files and diffs are read from the daemon when you ask, and only from folders the daemon's owner added.
What the cloud keeps
Who started each chat, where it runs, its title, model, mode and state. Nothing the agent says.
Your own usage
The cloud calls the daemon with a key minted for you and never shown, so your budgets, model access and audit trail apply. It is revoked when you leave the organisation.
Pricing
Included in Team and up, from $249/month
Venom Agents comes with the plan, like the rest of the workspace. There is no charge per seat or per chat.
- Owners, admins and developers start chats; owners and admins can also read everyone's
- Model calls are booked to the member who started the chat, against their budgets
- Without it, the app shows how to add it and the API answers 403 addon_required
Questions
Frequently asked
Do I need my own machine?
Can the agent reach files outside the project?
Can someone else on my team send to my chat?
What happens when my daemon restarts?
Talk to your agents from anywhere
Connect a daemon, add a project folder and start a chat.