Docs
Everything you need to install Operator, sign in once, and drive it from the terminal, your phone, or the web.
Getting started
Install the CLI globally with npm, then authenticate once — the same account works everywhere.
$ npm i -g @0perator/operator $ operator auth login # choose: email code · SMS code · Google · Microsoft
Sign in
Operator uses a single allow-listed account across every surface. Sign-up is self-serve; new accounts are reviewed and approved by an admin before they can reach a workspace.
The CLI
The terminal is Operator's home surface — a fast, native agent loop that reads, edits, greps, and runs commands in your repo, with every mutating step gated behind your approval.
$ operator "add rate limiting to the API and write the tests" ✷ reading src/api … editing 3 files … running tests … ✓ 42 passing
iOS app
The native app carries the same account and session history. Create and open files on-device, keep every past conversation searchable, and jump into a live remote-control session started from your terminal.
Remote control
Run /remotecontrol inside any session to get a shareable link. Open it at 0perator.co/session/<id> in any browser to watch the transcript, tool calls, and prompts live — and to steer the session from your phone or a teammate's laptop.
$ operator /remotecontrol ✷ remote control LIVE — continue at https://0perator.co/session/8f2a1c
Command reference
| Command | What it does |
|---|---|
| /remotecontrol | Publish the current session to a shareable web link for live viewing and steering. |
| /services | Check and manage which Operator-owned services (Aurora, automation daemons) are running. |
| /model | Switch the model backing the current session — Aurora 1M, or a frontier model. |
| ask_user | The agent's tool for pausing to ask a free-text or multiple-choice question mid-task. |
Links
Remote MCP & skills hub →
Create an account or request enterprise access →
operator.axe.onl — the MCP & skills hub →