---
title: Terminal quickstart
description: Install Orchestor CLI and retrieve brands, tracked questions, and
  visibility reports.
canonical_url: https://orchestor.io/docs/en/terminal-quickstart
markdown_url: https://orchestor.io/docs/en/terminal-quickstart.md
contentType: tutorial
---

# Terminal quickstart

Explore how your brand appears in AI search from your terminal. By the end of this guide, you can retrieve brands, tracked questions, and visibility reports, then continue investigating with an agent.

## Before you begin

- Open a terminal on macOS, Linux, or Windows. If this is your first time, see the [terminal guide](https://orchestor.io/docs/en/terminal-guide.md).
- Have an Orchestor account. [Create an account](https://orchestor.io/signup) if you need one.
- Have a workspace with brands and tracked questions configured. Follow the [Web quickstart](https://orchestor.io/docs/en/web-quickstart.md) for initial setup.

## Step 1: Install Orchestor CLI

Choose one method for your environment.

### macOS / Linux

```sh
curl -fsSL https://orchestor.io/install | sh
```

The native CLI does not require Node.js. On Alpine Linux, run `apk add --no-cache libstdc++` first.

### Windows

Download the ZIP for your architecture from the [latest release](https://github.com/orchestor-inc/cli/releases/latest) and extract it. Add the directory containing `orc.exe` to PATH, then open a new terminal.

### npm

You need Node.js 24 or later.

```bash
npm install -g @orchestor-inc/cli@latest
```

Verify your installation:

```bash
orc --version
orc --help
```

Installation is complete when the version and command list appear. If `orc` is not found, reopen your terminal and check the [installation guide](https://orchestor.io/docs/en/cli/installation.md).

## Step 2: Sign in to your account

```bash
orc auth login
```

Complete sign-in in your browser, then return to the terminal. Check your authentication status:

```bash
orc auth status
```

## Step 3: Select a workspace

List the workspaces you can access:

```bash
orc workspaces list
```

Copy the ID of the workspace you want to investigate. Replace `WORKSPACE_ID` with that value:

```bash
orc workspace use WORKSPACE_ID
orc workspace current
```

When your selected workspace appears, you are ready to investigate. Brands and questions already configured on the Web are available here too.

## Step 4: View your first results

Check your registered brands and tracked questions:

```bash
orc brands list
orc prompts list
```

Then retrieve the visibility report:

```bash
orc reports visibility get
```

If the results are empty, check the workspace, brands, questions, and measurement status in the Web app. Missing data does not mean visibility is zero.

Add `--json` to use the results in another tool:

```bash
orc reports visibility get --json
```

See [key visibility metrics](https://orchestor.io/docs/en/visibility/metrics-overview.md) for help interpreting results.

## Step 5: Investigate with an agent

To continue in Claude Code, Codex, Cursor, or another supported agent, follow the [agent setup guide](https://orchestor.io/docs/en/agent-setup.md). Ask your connected agent:

```text
Review the questions tracked in this workspace.
Find questions where competitors are mentioned but our brand is missing.
Show the supporting AI answers and cited sources.
```

Review the results, then narrow your investigation:

```text
Compare the pages cited for those questions.
Identify information missing from our site and suggest which pages to improve next.
```

## Essential commands

| Command | Purpose |
| --- | --- |
| `orc --help` | List available commands |
| `orc auth status` | Check authentication status |
| `orc workspaces list` | List accessible workspaces |
| `orc workspace use WORKSPACE_ID` | Select a workspace |
| `orc workspace current` | Check the selected workspace |
| `orc brands list` | Check registered brands |
| `orc prompts list` | Check tracked questions |
| `orc reports visibility get` | Retrieve the visibility report |
| `orc update --check` | Check the update method and latest version |

Append `--help` to a command for its arguments and options.

## Next steps

- [CLI workflows](https://orchestor.io/docs/en/cli/workflows.md): investigate competitors, answers, and sources
- [Agent setup](https://orchestor.io/docs/en/agent-setup.md): continue with your preferred agent
- [CLI updates](https://orchestor.io/docs/en/cli/update.md): find the update procedure for your installation method

## Get help

If `orc` is missing or starts a different version, run `type -a orc` on macOS / Linux or `Get-Command orc -All` in PowerShell. Check which installation is on your PATH.

For sign-in or workspace selection problems, check `orc auth status` and `orc workspace current`. If a shared workspace is missing, ask your administrator to confirm access.

See [troubleshooting](https://orchestor.io/docs/en/troubleshooting.md) for more help.

---

[Documentation index](https://orchestor.io/docs/llms.txt)