--- title: "Install rote — rote™ by modiqo" description: "Install the rote CLI (curl one-liner) and the rote VS Code extension. Both share the same ~/.rote state." doc_version: "1.1" last_updated: "2026-05-01" canonical: "https://modiqo.ai/docs/rote-install.txt" --- # Install rote > **Install once, work from anywhere.** The CLI and the VS Code extension share `~/.rote/` state — pick either or use both side by side. Two surfaces. Install whichever fits your workflow — they share the same `~/.rote/` state, so you can use both side by side. ## rote CLI The local-first command-line surface. Wizard-guided install: ```bash curl -fsSL https://getrote.dev/install | bash ``` The installer drops the `rote` binary on your `PATH` and launches an interactive wizard that walks you through: 1. Registry sign-in (request invite or claim an existing one) 2. Adapter selection from the catalog 3. OAuth and token configuration for the adapters you picked 4. Skill / agent wiring for Claude Code and other AI clients 5. A live proof-of-life run against each configured adapter After the wizard finishes, your environment is set up at `~/.rote/`. From there: ```bash rote how # onboarding tree — start here rote guidance agent essential # 700-line agent steering guide rote flow search "" # find a ready-made flow ``` ## rote VS Code extension The visual surface for the same `~/.rote/` state — sidebar trees, panels, setup wizard, run-flow UI, and a registry browser. 1. Open VS Code. 2. Go to **Extensions** (`Cmd+Shift+X` on macOS, `Ctrl+Shift+X` on Windows / Linux). 3. Search for **rote**. 4. Click **Install**. 5. The extension opens its setup wizard. From the wizard: - **Request invite** — if you don't have a registry account yet. - **Claim invite** — if you have an invite code from your team. - **SSO** — sign in to the registry with your existing identity provider. 6. Once signed in, the wizard mirrors the CLI flow: select adapters, configure tokens (OAuth for Google services, paste-in for static API keys), and run a live proof against each. The extension uses the rote CLI under the hood — so installing the CLI first is recommended but not required. The extension will guide you through CLI setup if it isn't found. ## Which to use - **CLI only** — best for terminal-native workflows, agent runners (Claude Code, Cursor agents), CI machines, and headless servers (use `rote provision` / `rote claim` for those). - **VS Code extension** — best for visually browsing your adapters, flows, and traces; running flows with parameter forms; reviewing registry artifacts; and onboarding teammates. - **Both** — they share `~/.rote/`. Changes made by either are visible to the other immediately (the extension watches the directory). ## What gets installed - `~/.rote/` — all local state (adapters, flows, secrets, registry config, workspaces, archives). - `rote` binary — typically at `~/.local/bin/rote` or `~/.cargo/bin/rote` depending on platform. - Embedded Deno runtime — auto-installed on first flow run, lives at `~/.rote/bin/deno`. - TypeScript SDK — `~/.rote/lib/sdk/ts/` for flow authoring. See [/docs/rote-architecture.txt](https://www.modiqo.ai/docs/rote-architecture.txt) for the full on-disk layout. ## Verify the install ```bash rote --version rote config check # validate environment rote adapter list # show installed adapters rote token list # show configured tokens (no secrets shown) ``` If `rote config check` reports any missing pieces, re-run the wizard: ```bash rote setup ``` ## Updating ```bash curl -fsSL https://getrote.dev/install | bash ``` The installer is idempotent — re-running upgrades the binary without disturbing `~/.rote/`. Your adapters, flows, secrets, and registry session are preserved. For the VS Code extension, updates flow through the marketplace — VS Code will notify you when a new version is available. ## Uninstall ```bash rm -rf ~/.rote # all state rm "$(which rote)" # the binary ``` Uninstall the VS Code extension from the Extensions panel. > **Heads-up:** removing `~/.rote/` deletes encrypted tokens. Push the vault to the registry first if you want to recover them on another machine: `rote vault push`.