CLI Reference¶
StackOps currently exposes two entry styles:
- standalone commands such as
devops,fire, andseek - umbrella wrapper:
stackops
For day-to-day use, prefer the standalone command when you already know which tool you want. Use stackops when you want one top-level CLI that routes into the same command tree.
Standalone entrypoints¶
| Command | Purpose |
|---|---|
devops |
Package installation, repo automation, config sync, data sync, self-management, networking, and script execution |
terminal |
Terminal session and layout management |
agents |
AI agent scaffolding, MCP catalog installs, prompt runs, and parallel agent workflows |
utils |
General-purpose utility commands |
croshell |
Cross-shell launcher built around uv run backends |
seek |
Interactive search across files, text matches, and symbols |
fire |
File, function, notebook, and app runner |
cloud |
Cloud sync, copy, mount, and SSH transfer helpers |
Umbrella entrypoints¶
stackops is a lazy-loading wrapper around the same top-level command families:
The wrappers currently expose:
devopscloudterminalagentsutilsseekfirecroshell
For the full command-specific flag surface, check the standalone command as well, for example fire --help or seek --help.