Anysola CLI
Your control plane,
in the terminal.
Deploy agents, run operations, and inspect usage from SSH sessions, CI runners, and automation — with the same audit trail and workspace boundaries as the dashboard.
npm install -g @anysola/cli $ anysola login --label prod-batch-01
Open in your browser:
https://anysola.com/cli/activate?code=ABCD-1234
Your code: ABCD-1234
Waiting for authorization…
✓ Signed in as ops@company.com
Workspace: Production (admin)
$ anysola agents run 665f1c… --action SYNC_LEDGER
operation 665f2a… · ok · SYNC_LEDGER
Up and running in three commands.
No API keys to paste on shared servers. Authorize once in the browser; the CLI stores rotating OAuth tokens locally.
-
01
Install
One global package. Works on macOS, Linux, and Windows terminals.
npm install -g @anysola/cli -
02
Authorize
Run login, open the browser once, pick your workspace. OAuth device flow — no passwords in the shell.
anysola login -
03
Operate
Deploy agents, run operations, and read usage from CI, SSH, or your laptop.
anysola agents list
Why teams use the CLI
-
Full workspace API
List and deploy agents, trigger runs, read activity, usage, integrations, and audit events — without opening the dashboard.
-
OAuth device login
Sign in through anysola.com in your browser. Tokens stay on the machine; revoke sessions anytime from Settings.
-
Built for servers
Headless-friendly output with --json. Preemptive token refresh. Clear exit codes for scripts and pipelines.
-
Role-aware access
Scopes mirror your workspace role. Viewers read; members run agents; admins manage settings and integrations.
Command surface
Every command talks to the same API as the dashboard. Pass --json for scripts.
-
anysola loginDevice-flow auth -
anysola whoamiWorkspace + plan -
anysola agents listAll agents -
anysola agents run <id>Record an operation -
anysola usageMonthly quotas -
anysola activityOperation log -
anysola settings getWorkspace prefs -
anysola integrations listConnected systems
Security
Browser login, machine-scoped tokens
The CLI uses OAuth 2.0 device authorization. You approve access at anysola.com/cli/activate while signed in. Access and refresh tokens are stored in ~/.anysola/credentials.json with restrictive permissions.
- Revoke CLI sessions from Dashboard → Settings
- Refresh token rotation on every renewal
- API keys remain separate — for CI, not interactive login
Ready to wire Anysola into your stack?
Install the CLI, run anysola login, and manage
agents from anywhere you already work.