The Space Agent CLI lives in a single entry file —Documentation Index
Fetch the complete documentation index at: https://mintlify.com/agent0ai/space-agent/llms.txt
Use this file to discover all available pages before exploring further.
space.js — and exposes all server management, configuration, and state-management operations through a consistent node space <command> interface. Commands are discovered dynamically: every .js file inside the commands/ directory is treated as a command module, so the command set reflects exactly what is present on disk. There are no hidden built-ins beyond the two flag aliases --help and --version.
Entry Point
Run any command with Node directly, or markspace.js executable first:
| Flag | Resolves to |
|---|---|
--help | help |
--version | version |
Command Families
Space Agent groups its commands into two families based on what they affect.Operational
Control or inspect the local runtime:
serve, supervise, help, get, set, version, updateState Management
Edit layered runtime data under the logical app tree:
user, groupAll Commands
| Command | Summary | Usage |
|---|---|---|
serve | Start the local Node server | node space serve [PARAM=VALUE ...] |
supervise | Run a zero-downtime reverse-proxy supervisor | node space supervise CUSTOMWARE_PATH=<path> [...] |
user | Create users and manage passwords | node space user <create|password> ... |
group | Create groups and manage membership | node space group <create|add|remove> ... |
get | Read server config parameters from .env | node space get [PARAM] |
set | Write server config parameters to .env | node space set KEY=VALUE [...] |
update | Update source checkout from Git | node space update [target] |
version | Print the git-derived project version | node space version |
help | List commands or show per-command help | node space help [command] |
Built-in Help
Every command module exports ahelp object that node space help uses to generate output. You never need to read the source to find the correct flags.
Command Discovery
Thespace.js loader reads commands/*.js at runtime and sorts the results alphabetically. Any .js file placed in that directory becomes a command. Non-JavaScript assets such as commands/params.yaml and subdirectories like commands/lib/ are intentionally excluded from discovery — only files matching the pattern commands/<name>.js are loaded.
Because command names derive from filenames, the command set can differ between source checkouts at different revisions. Run
node space help to see exactly which commands are available in your current checkout.