Use the CLI When
Reach for the CLI for workflows that are naturally scriptable:- install, auth, and version management
- config-driven deploys and restarts
- env vars, domains, logs, releases, and rollbacks
- spend caps and billing upgrade flows
- organization member listing and role changes
- agent automation through
--json
Use the Dashboard When
Reach for the dashboard when you want a visual view or when the flow is currently dashboard-first:- Apps overview and service map
- Monitoring charts and org analytics
- per-app end-user management for
floo_accounts - domain allowlists
- GitHub connection UI inside app settings
- password display for password-protected apps
- profile and API key management
Current Split
| Workflow | CLI | Dashboard |
|---|---|---|
| Deploy and restart | first-class | view status |
| Runtime logs and build logs | first-class | visual app detail |
| Releases and rollbacks | first-class | Releases tab |
| Spend cap and upgrade | first-class | Billing page |
| Org team roles | first-class | Team page |
| App users and domain allowlists | not first-class | first-class |
| Profile and API keys | limited | first-class |
For Agents
Agents should default to the CLI because:- every command supports
--json - stderr stays human-oriented while stdout stays machine-readable
- the command tree is discoverable with
floo commands --json - the built-in CLI docs are available through
floo docs
Recommended Pattern
Use the CLI as the source of operational truth, and use the dashboard when a human needs:- a service map
- plan/usage charts
- account settings
- user-management views