00Docs
Read the manual.
Each product's docs live in its own repo and are pulled in at build time. The spec, the RFCs and the ecosystem decisions are under spec.
02venomx
OverviewA headless terminal multiplexer that humans and agents drive through the same verbs.72dc386 →Getting startedvenomx is in alpha. Each release ships a static Linux x8664 binary that runs on any distribution:72dc386 →Keys and the attach clientvenomx attach (and the bare venomx) draws a session in your terminal. It is one client among many: what it shows comes from the daemon, and what you change locally (focus,…72dc386 →Configurationvenomx reads ZON, Zig's data notation. There is no scripting: config is data, checked against a schema before anything uses it.72dc386 →Status lineThe status line is a row of segments on three sides: left, center and right. venomx draws its own (venomx.session, venomx.windows, ...), and anything with the right grant can…72dc386 →AgentsDrive venomx from Claude Code, Codex, opencode or a script, over the CLI or MCP.72dc386 →Isolation, owners and namespacesWhy your scripts just work by default, and how to keep agents apart when you need to.72dc386 →Daemon lifetime and recoveryThe daemon holds everything: every process, every screen, every session. This page covers when it starts and stops, how panes end, and how to keep a record of your layout…72dc386 →Performancevenomx keeps a full terminal emulator per pane in the daemon and another in each attached client, and still aims to be at least as fast as the multiplexers it replaces.…72dc386 →Command referenceEvery venomx verb, its flags, result and errors, generated from the verb schema.72dc386 →