One launcher. Tools when you need them.
Install the umbrella sys9 CLI, then launch the supported tools through
sys9 run, sys9 db, sys9 smith, and other listed
subcommands. Tools install on first use. Complete each product’s login or workspace
setup before using its services.
Install sys9. Start with one product.
The npm package installs the launcher. It reuses an installed tool or downloads it
on demand. Use sys9 <tool> consistently: managed db9 and drive9
binaries live under ~/.sys9/tools and are not automatically put on
your PATH. The database example creates real resources.
# install the launcher; tools install on first use $ npm install -g @sys9/cli $ sys9 status # create a database, then query it $ sys9 db create --name my-app $ sys9 db sql my-app -q "SELECT 1" # check another service's authentication requirements $ sys9 run auth login --help
The current CLI catalog.
Each listed sys9 <tool> launches its product CLI. Run that command with --help to inspect the installed version.
run9
Linux Boxes, filesystem Snaps, and remote command execution.
run9 → sys9 dbdb9
Serverless Postgres with database branching and file storage.
db9 → sys9 drivedrive9
Persistent files, semantic search, and explicit vault grants.
drive9 → sys9 owlowl9
Capture supported agent sessions after space and runtime setup.
owl9 → sys9 tasktask9
Shared tasks with atomic claims and optional owner-liveness.
task9 → sys9 inboxinbox9
Messages with explicit read marks and a retention window.
inbox9 → sys9 pulsepulse9
Worker leases and heartbeats; applications handle recovery.
pulse9 → sys9 tapetape9
Append-only logs with snapshot reads and explicit streaming.
tape9 → sys9 smithsmith9
Configure providers, create Envs and Sessions, and submit Turns.
smith9 → sys9 chordchord9
Set up and manage a local Host for the chord9 workbench.
chord9 →Independent installers are available too.
Follow the product’s own installation guide when you want its executable on PATH. Installing the umbrella launcher alone does not install every bare command.
Follow the run9 quickstart for its installer, authentication, and Box workflow.
Installation guide → db9Use the standalone db9 installer documented in its quickstart.
Installation guide → drive9Install the native drive9 CLI for your platform, then configure a workspace.
Installation guide → owl9Install owl9 and configure your space and supported runtime integration before capture.
Installation guide →Separate integrations and planned products.
mem9 has its own setup. The remaining products below are planned directions; no release date or CLI availability is promised.
Memory is available through its documented API and runtime integrations; it is not in the sys9 CLI catalog.
mem9 →Planned identity service. Use current product authentication today.
auth9 →Planned model gateway; no current sys9 subcommand.
gate9 →Planned managed browser service; no current sys9 subcommand.
web9 →Planned registry for skills and tools; no current sys9 subcommand.
hub9 →Planned standalone credential management; no current sys9 subcommand.
vault9 →Planned agent evaluation tools; no current sys9 subcommand.
eval9 →Planned scheduling service; no current sys9 subcommand.
cron9 →A CLI for humans and agents.
Use the same commands interactively or in automation, with the credentials and permissions each service requires.
Agent-native
Structured resource commands support JSON where documented. Interactive commands and output streams retain their native format; for example, run9 box exec does not support --json. Check each command’s help.
Authentication belongs to each product
Installing the CLI does not require a service account. run9 and smith9 require authentication, chord9 connects a signed-in workbench to a Host, and private message or transcript spaces need a secret before first use.
Install sys9. Start composing.
Install the CLI from npm and choose a product setup guide. Contact us for access requirements or help with your workload.