One install. Every sys9 tool.
The umbrella sys9 CLI installs and launches everything — sys9 run,
sys9 db, sys9 smith, sys9 drive, and the rest. Every
tool also ships as a bare CLI you can run on its own. Agent-native and use-first,
claim-later: there's no signup to get started — point an agent at the same CLI and go.
Install sys9. Launch everything.
One binary installs and launches the whole stack. Drive any tool through
sys9 <tool>, or reach for the bare CLI — db9,
run9, drive9 — when you only want one. Same tools either way.
# one install — the umbrella sys9 CLI $ npm i -g @sys9/cli ✓ sys9 installed # launch any tool through sys9 … $ sys9 run fork my-box $ sys9 db query "select 1" $ sys9 drive mount :/data ~/data # … or use the bare per-tool CLI directly $ db9 branch my-app review ✓ same tool · no signup to start
Every tool, under sys9.
One install puts the whole stack a subcommand away. Each sys9 <tool> launches the matching service.
run9
Forkable Linux sandboxes — fork the whole OS in ~50ms.
run9 → sys9 dbdb9
Serverless Postgres with branching and file storage.
db9 → sys9 drivedrive9
One shared filesystem across every sandbox and session.
drive9 → sys9 owlowl9
Zero-config agent session observability.
owl9 → sys9 tasktask9
Atomic task claim — distributed work-claim.
task9 → sys9 inboxinbox9
Agent-to-agent messaging — FIFO per recipient, guaranteed delivery.
inbox9 → sys9 pulsepulse9
Liveness leases and heartbeats — powers task9 ownership.
pulse9 → sys9 tapetape9
Append-only streams with real-time replay.
tape9 → sys9 smithsmith9
Agent as a service — host fleets on run9.
smith9 → sys9 chordchord9
Agents and humans, one team — built for long runs.
chord9 →Every tool is also a CLI of its own.
Prefer one tool, not the suite? Each ships as a bare, focused CLI — small surface, less agent context, fewer tokens.
run9 fork my-box · drive 100 sandboxes in parallel.
db9 db create my-app · db9 query "select * from notes".
drive9 fs grep "pricing strategy" / · semantic search.
OWL9_ENABLE=1 claude · wrap the binary, capture the session.
task9 create "Triage flaky deploy" · task9 claim 41.
tape9 capture deploy-log -- ./deploy.sh · tape9 read.
inbox9 send bob --payload … · inbox9 wait bob.
pulse9 — liveness leases and heartbeats; powers task9.
Eight more CLIs, coming soon.
CLIs that haven't shipped yet. Preview each concept and request early access.
Agent memory — one memory, many agents. The service is ready; its CLI is on the way.
mem9 →One identity, any sys9 — sign in once, unlock every service.
auth9 →Model gateway — one endpoint for every model: routing, caching, cost caps, fallback.
gate9 →Managed headless browsers for agents — sessions, stealth, captcha, screenshots.
web9 →Skills & tools registry — publish once, any agent installs.
hub9 →First-class secrets — per-agent grants, rotation, sealed delivery.
vault9 →Evals for agents — offline suites and online quality.
eval9 →Scheduling — run agents on a schedule or on events and webhooks.
cron9 →Agent-native, use-first.
The CLI is designed for agents to drive — and for you to start before you sign up.
Agent-native
Agent-friendly commands, predictable output, and --json on every command. The same surface works for a human at a terminal and an agent in a loop.
Use-first, claim-later
No signup wall before the first command. Start working immediately, claim the account when you're ready — the way every sys9 tool is meant to be used.
Install sys9. Start composing.
sys9 is in closed beta. Tell us what you're building and we'll get you set up with the CLI.