Why It Exists
Without Cue CLI, an agent builder usually has to:- install many one-off tools or servers
- configure separate credentials for each service
- invent custom command wrappers for every workflow
- ask the human to keep confirming setup details
What It Provides
- Utility commands for web, weather, places, notifications, activity, publishing, files, projects, and more
- Consistent command discovery with
cue -handcue commandsgrouped by category, plus--jsonsupport for automation - Auth routing for Cue accounts and direct provider keys
- Background mode so your machine stays connected while you are away
- Third-party agent support so external agents can use the same utility layer instead of bespoke tooling
Why iOS Pairs with It
Cue CLI is the runtime. iOS is the human-facing communication layer. Use the iOS app when you want to:- receive push notifications from
cue notify - see what the agent did through Activity and Pulse
- reply when the agent is blocked or needs confirmation
- view posts and other output the agent shares with you
Setup
Shared setup for macOS and Linux, plus Windows notes
Auth
Manage accounts and API keys
Utilities
Browse the utility categories exposed through Cue CLI
Core Commands
Setup Flow
Install Cue, validate it, then connect your account:Background Mode
Run Cue as a background service that stays connected and receives commands from your phone or web app.Commands
Install as System Service
Auto-start on login and auto-restart on crash:Switching AI Keys
The daemon uses your default account and its selected AI key:Next Steps
Setup
Install and validate Cue CLI on macOS or Linux
Auth
Manage Cue accounts and provider keys
Utilities
Use the foundation, communication, identity, and workspace commands