> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remoteagent.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> From zero to a working Telegram-controlled AI agent in under five minutes.

<Note>
  Your API key never leaves your machine. RemoteAgent.CHAT is a pure relay — it
  routes messages between Telegram and your local agent without storing or
  inspecting your credentials, prompts, or code.
</Note>

<Steps>
  <Step title="Install the agent">
    Download and install the RemoteAgent.CHAT binary with a single command:

    ```bash theme={null}
    curl -fsSL https://remoteagent.chat/install | bash
    ```

    Verify the installation:

    ```bash theme={null}
    remoteagent --version
    ```

    The binary is self-contained — no Node.js or runtime required. Runs on Linux, macOS, and Windows (WSL recommended on Windows).
  </Step>

  <Step title="Install your runner (if needed)">
    RemoteAgent.CHAT supports multiple AI runners. The default is `claude-code` — requires the `claude` CLI installed and authenticated. Other runners require their own binary installed first.

    | Runner        | Prerequisite                                                |
    | ------------- | ----------------------------------------------------------- |
    | `claude-code` | `npm install -g @anthropic-ai/claude-code` + `claude login` |
    | `claude-sdk`  | None — runs in-process. Needs an Anthropic API key.         |
    | `opencode`    | `npm install -g opencode-ai`                                |
    | `gemini`      | `npm install -g @google/gemini-cli`                         |
    | `aider`       | `pip install aider-chat`                                    |
    | `openclaw`    | OpenClaw daemon running on port `18789`                     |
    | `custom`      | Any binary that reads stdin and writes stdout               |

    See [Runners](/runners/overview) for details on each option.
  </Step>

  <Step title="Get your pairing code from the dashboard">
    Log in to [remoteagent.chat](https://remoteagent.chat) with the Telegram widget.

    Once in the dashboard, click **Pair new agent**, enter a project name, and confirm. The dashboard will display a **pairing code** — a short string like `XK9-4TZ`.

    <Warning>
      The pairing code expires in **10 minutes** and can only be used once.
      Keep the dashboard tab open while you complete the next step.
    </Warning>
  </Step>

  <Step title="Run the init wizard">
    Navigate to the project directory you want to control, then run:

    ```bash theme={null}
    cd /path/to/your/project
    remoteagent init
    ```

    The interactive wizard will ask you:

    * **Runner** — which AI engine to use. Press Enter to accept the default (`claude-code`), or type a runner name.
    * **API key** — only required for runners that need one. Stored locally in `~/.remoteagent/agents/{agentId}.json`, never transmitted.
    * **Pairing code** — paste the code you got from the dashboard in the previous step.

    Once the code is accepted, the agent is paired and starts automatically.
  </Step>

  <Step title="Send your first command">
    Open Telegram, find the **RemoteAgent.CHAT bot** (a link is shown after pairing), and send a message:

    ```
    List the files in this project and describe what each one does
    ```

    The agent will start running immediately. Output streams back to Telegram in real time as the AI produces it. Long responses are split into multiple messages automatically.

    Try a more targeted task:

    ```
    Fix any TypeScript errors in src/api/users.ts
    ```

    To abort a running task at any time, send:

    ```
    abort
    ```
  </Step>
</Steps>

## Updating

```bash theme={null}
remoteagent reinstall
```

This updates the binary in-place and automatically restarts any running agents.

## What's next

* Learn about all available [runners](/runners/overview) and how to switch between them.
* Set up [multiple projects](/bot/multi-project) to control different codebases from the same bot.
* Explore the [dashboard](/dashboard) to view session history and manage your account.