## Three execution modes Orb decouples **where you read and steer** from **where the agent executes**: | Mode | Where it runs | How you use it | | --- | --- | --- | | **Your computer** (`placement: "client"`) | Locally on your Mac via Orb's Tauri runner | Choose **New Agent → This computer**, then a local CLI (**Claude Code**, **Codex**, **Antigravity**, **OpenCode**, or **Grok**). Uses your local files, tools, and existing CLI logins while keeping project records and mission transcripts synced to your server. | | **Your private cloud** (`core` or `remote_node_id`) | Your own Linux servers and fleet nodes | Run agents on the Core server or leased `sandboxed-node` machines in host directories or isolated `systemd-nspawn` containers with cgroup resource caps. | | **Cloud agents** | Coordinator or provider-managed services | Choose **Cloud agent**, then **Hermes**, **ChatGPT**, **Grok Bot**, or **Cursor Cloud**. Continue durable coordinator sessions or provider conversations directly from Orb. | ## Pick up the conversation anywhere Projects organize missions, per-project colors, native skills (`skills//SKILL.md`), and a bi-directionally synchronized **Context** folder (`@context`). Inside a conversation: - **Follow and steer live runs**: collapsible activity and thought folds, nested subagents, `/plan` mode with native question and approval cards, `/goal` mode for autonomous multi-turn execution, and a durable follow-up queue that sends on turn completion or immediately. - **Ask on the side (`/btw`)**: open the docked side-agent panel (`⌘⇧J`) to ask questions with shared workspace context and `@conversation` snapshots without interrupting the main agent turn. - **Keep long work moving**: schedule durable mission wake-ups (`schedule_wakeup`), automatically recover interrupted runs, and **transfer missions across machines** (`Change machine…`) with SHA-256 verified file manifests and Git bundles. - **Rich output**: Markdown, syntax-highlighted code, tables, KaTeX math, interactive quizzes, inline images, and clickable workspace file links (`⌘J` / `⌘P`). Orb for **iOS** connects to the same server: browse projects with synced colors, inspect mission transcripts and activity folds, send follow-ups, edit shared Markdown context, and manage your backend, machines (with a shared SSH address book), and providers. ## Bring your subscriptions Sign in to supported subscription accounts directly from **Providers** in Orb (macOS, web, and iOS) or connect them through **CLIProxyAPI Plus**. When `SANDBOXED_OAUTH_OWNER=cli-proxy` is enabled, CLIProxyAPI owns OAuth token refresh for Anthropic, OpenAI, xAI, Kimi, and Google Antigravity, preventing refresh-token race conditions across processes while Orb lets you inspect live plan and quota status and route model inference. ## Next steps 1. **[Getting Started](/getting-started)**: Connect Orb on macOS and iOS, configure providers, and launch your first agent. 2. **[Server Setup](/setup)** or **[Docker Install](/install-docker)**: Deploy the backend on Linux or Docker. 3. **[Machines & Workspaces](/workspaces)**: Understand local runs, remote fleet nodes, `systemd-nspawn` containers, and mission transfers. 4. **[Skills, Context & Library](/library)**: Synchronize project skills, `@context` files, and the Git-backed Library. 5. **[API & MCP Reference](/api)**: Integrate with the REST API, SSE stream, and unified `sandboxed-mcp` server.