Venom · P0 Foundations · In developmentVenom
Many fangs, one bite.
An agent-friendly OS that lives in the terminal. You and your coding agents work in the same panes, through the same verbs.
- Youyour agentsClaude Code · Codex · opencode · ACPThe agents you already use, through their official channels.
- 02venomorchestrator(coming…)One git worktree per agent per repo, one inbox for approvals.
- 01venomxmultiplexerSessions, windows and panes in one daemon.
venomx - 00venom-osthe bundle(coming…)Supervises venomx, venom, venom-desk and venom-mem with curated defaults.
Zig 0.17 / TUI first
Agents in panes.
venom places each agent in its own venomx pane, on its own worktree. You watch, approve and take over from the same session.
task port the status line to the tray fan-out 3 agents · 3 worktrees ◆ running claude-code venomx-201 ▲ approval codex venom-desk-88 wants to run zig build test ● done opencode venom-term-57 a approve d deny ⏎ open pane █
▸ editing src/status.zig + .tray = .{ .group = "agents" }, - .right = "%H:%M", // 14 files, +312 −97
$ venomx capture --pane %3 --json | jq .lines [ "All 412 tests passed." ]
An OS for working with agents, not another agent.
The multiplexer and the orchestrator are one family, held together by one contract. A human at the keyboard and an agent over MCP drive the same panes with the same verbs.
Let them run on Monday. Read the event log on Tuesday.
Agents are fast and confidently wrong. So Venom has two jobs: give each one a room of its own, and keep you one keystroke away from every decision that matters.
Every action is a verb.
One verb schema generates the CLI, the MCP server, the docs and the completions. What you type, an agent can call.
Bring your agents.
Claude Code, Codex, opencode and ACP agents, through their official channels. We orchestrate them; we never spoof them.
Read-only until granted.
Capability grants keep every caller read-only until you hand it more. Approvals land in one inbox.
Everything, in one bite.
venom-os up supervises the whole family with curated defaults. Each piece also stands on its own.
venom(coming…)The orchestrator of coding agents
venomx11The multiplexer agents can drive
venom-os(coming…)The bundle- venom-desk(coming…)The TUI desktop on venomx
- venom-mem(coming…)Shared memory for agents
- venom-std1Shared Zig modules
- venom-term1The terminal API
Built to be driven.
Every binary follows the same contract, so an agent that learns one learns them all. Read the foundations.
- One binary
- The daemon and its CLI are one binary.
$ venomx serve - Structured
- --json on every command, stable exit codes.
$ venom doctor --json - Observable
- An NDJSON event stream for every daemon.
$ venomx events --json - Teachable
- skill teaches an agent the binary it runs.
$ venomx skill
Common questions.
What is Venom?
An agent-friendly OS that runs in the terminal. venomx is the multiplexer, venom is the orchestrator, and venom-os bundles them with venom-desk and venom-mem. Humans and coding agents work in the same panes.
Is Venom another coding agent?
No. Venom orchestrates the agents you already use (Claude Code, Codex, opencode, ACP agents). It does not ship its own agent runtime or harness.
How do agents drive it?
Every binary follows the agent contract: verbs exposed as CLI and MCP, --json output, an event stream, a skill command and capability grants.
Does it need a desktop?
No. It is TUI first. Everything runs in a terminal, locally or over SSH on a devbox.
Can I try it today?
venomx is in alpha: download a static Linux x86_64 binary from its latest release, or build it from source with Zig 0.17. venom, venom-desk and venom-os are coming.