Use Supen in the CLI

The CLI is the fastest interface when you are already working in a terminal. It connects to the same Supen runtime as the platform, but it keeps your workflow closer to local files, shell tools, and quick iteration.

First-time setup

Use these commands when you are setting up a local or self-hosted Supen environment:

supen bootstrap
supen start
supen status

supen bootstrap handles initial configuration. supen start brings the service online. supen status confirms whether the service, channels, and detected coding CLIs are available.

Common day-to-day commands

Start a chat with an agent

supen chat "Summarize what this space is for" --agent web-agent

This opens a session if needed, streams the answer, and keeps you in the terminal.

Check spaces

supen space list

Use this when you want to see the spaces available through the gateway.

Launch a new space

supen space launch my-space --mode blank --tier nano --region local

You can also launch from:

• a template with --mode template --template <id>
• a snapshot with --mode snapshot --source-space <id>

Inspect agents and sessions

supen agent list
supen session list

Use these when you need to see what already exists before starting more work.

Diagnose runtime issues

supen daemon status
supen daemon logs --lines 100

These are the fastest checks when the CLI or platform feels disconnected.

When the CLI is the better choice

Prefer the CLI when:

• you are already in a repository
• you want fast iteration without switching windows
• the task depends on local shell tools
• you need to inspect or start the runtime directly

Switch back to the platform when you need broader visibility, easier space management, or shared review.