sys9 CLI

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 the CLI Read the docs →
One launchersys9 <tool>On-demand toolsProduct-specific setup
install once

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.

one install installs supported tools on demand service setup required
terminal
# 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
one umbrella

The current CLI catalog.

Each listed sys9 <tool> launches its product CLI. Run sys9 status to see installed and latest versions, and sys9 <tool> --help for usage.

sys9 run

run9

Linux Boxes, filesystem Snaps, and remote command execution.

run9 → sys9 db

db9

Serverless Postgres with database branching and file storage.

db9 → sys9 drive

drive9

Persistent files, semantic search, and explicit vault grants.

drive9 → sys9 owl

owl9

Capture supported agent sessions after space and runtime setup.

owl9 → sys9 task

task9

Shared tasks with atomic claims and optional owner-liveness.

task9 → sys9 inbox

inbox9

Messages with explicit read marks and a retention window.

inbox9 → sys9 pulse

pulse9

Worker leases and heartbeats; applications handle recovery.

pulse9 → sys9 tape

tape9

Append-only logs with snapshot reads and explicit streaming.

tape9 → sys9 smith

smith9

Configure providers, create Envs and Sessions, and submit Turns.

smith9 → sys9 chord

chord9

Launches the chord runner after a Host has been paired with the portal-provided setup command; pairing itself starts from the workbench.

chord9 →
bare CLIs

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.

run9

Follow the run9 quickstart for its installer, authentication, and Box workflow.

Installation guide → db9

Use the standalone db9 installer documented in its quickstart.

Installation guide → drive9

Install the native drive9 CLI for your platform, then configure a workspace.

Installation guide → owl9

Install owl9 and configure your space and supported runtime integration before capture.

Installation guide →
outside this catalog

Separate integrations.

mem9 has its own setup, and auth9 works behind the services that use it.

mem9 separate setup

Memory is available through its documented API and runtime integrations; it is not in the sys9 CLI catalog.

mem9 →
auth9 separate setup

Sign-in and credentials for services that use it. It has no sys9 subcommand; each product CLI handles its own login.

auth9 →
built for agents

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.

get started

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.

Open product docs See every product →