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

# Quickstart for agents

> Install the wat CLI and skills, log in once, then ask your agent to book a room.

This is the fast path **for humans**: in four steps you give an AI coding agent (Claude Code, Codex, …) the ability to book WAT rooms for you in plain language.

<Note>
  **Are you the agent?** You don't need any of this setup — follow the [Agent playbook](/agents) instead: it works immediately via `npx`, with no global install and no skills.
</Note>

<Note>
  **Using claude.ai or Claude Desktop (no terminal)?** Skip this page entirely: connect the [MCP server](/mcp-server) instead. One URL, sign in with your email, zero installation.
</Note>

<Note>
  **Prerequisites:** Node.js 20 or higher, and a WAT account. No account yet? Your first login creates one automatically if your **company email** is on WAT's resident list — see [Create an account](/account).
</Note>

<Steps>
  <Step title="Install the wat CLI">
    Install it globally so the `wat` command is on your PATH (the skills call it):

    ```bash theme={null}
    npm install -g @wat-toolbox/wat
    ```

    Check it works:

    ```bash theme={null}
    wat --version
    ```
  </Step>

  <Step title="Install the skills plugin">
    The skills wrap the CLI so your agent can book rooms conversationally.

    ```bash theme={null}
    npx plugins add WATbeta/wat-plugin
    ```

    In Claude Code you can use the native form instead:

    ```
    /plugin marketplace add WATbeta/wat-plugin
    /plugin install wat@wat-plugin
    ```

    The skills surface as `/wat:list-rooms`, `/wat:check-availability`, `/wat:book-room`, and `/wat:my-bookings`.
  </Step>

  <Step title="Log in">
    Run `wat login` once. It sends a 6-digit code to your email; entering it both logs you in and (on your **first** login with a resident-list email) creates your account.

    ```bash theme={null}
    wat login
    ```

    The CLI mints an API key and stores it locally (`~/.config/wat/config.json`, mode 0600). The skills reuse this stored key, so you authenticate once. Confirm with:

    ```bash theme={null}
    wat whoami
    ```
  </Step>

  <Step title="Ask your agent to book a room">
    With the CLI logged in and the skills installed, just ask in natural language:

    > Book me Room A tomorrow from 10:00 to 11:00.

    The agent resolves the room, checks availability, and creates the booking through the `wat:book-room` skill.
  </Step>
</Steps>

## Hand this to your agent

Don't want to run the steps yourself? Paste this into your agent and let it do everything (it will ask you for the email code):

```text theme={null}
Read https://docs.wat.com/agents (the WAT Rooms agent playbook)
and follow it. My email is <your email>. Book me Room A tomorrow from 10:00
to 11:00, and once that's done, set up the persistent CLI + skills install
for next time.
```

<Note>
  Use your company email: sign-up is automatic for resident company domains. If login is refused with `NOT_AUTHORIZED`, an access request is automatically sent to the WAT admins: you'll receive an email if it's approved, then log in again.
</Note>

## What's next

<CardGroup cols={2}>
  <Card title="The wat CLI" icon="terminal" href="/cli">
    Every command and flag, with copy-paste examples.
  </Card>

  <Card title="MCP server" icon="plug" href="/mcp-server">
    Book from claude.ai or Claude Desktop with no terminal and no install.
  </Card>

  <Card title="Booking rules" icon="book-open" href="/booking-rules">
    Durations, the 2-hour daily budget, the booking horizon, and more.
  </Card>
</CardGroup>