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

# Quick Start

> Sign up, install the CLI, connect to your account, and run your first verification.

## Prerequisites

* **Node.js 22 or later** check with `node --version`
* An AI coding client: [Claude Code](https://docs.anthropic.com/en/docs/claude-code), [Cursor](https://cursor.com), or [Codex CLI](https://github.com/openai/codex)

***

## Step 1 - Create your account

Go to [console.ironbee.ai](https://console.ironbee.ai) and sign up. Your account gives you access to the dashboard and generates the API key the CLI needs to ship session data.

***

## Step 2 - Install the CLI

```bash theme={null}
npm install -g @ironbee-ai/cli
```

Verify the installation:

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

***

## Step 3 - Connect the CLI to your account

Run `ironbee login` from any directory. It opens your browser at `console.ironbee.ai`, asks you to authorize the CLI, and writes a personal OAuth access token and collector URL to `~/.ironbee/config.json` automatically.

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

The browser opens, you confirm, and the terminal prints:

```
✓ Logged in successfully!
  Console   https://console.ironbee.ai
  Collector https://collector.service.ironbee.ai
  Token     personal (my-laptop)
  Config    ~/.ironbee/config.json
```

The token is named after your machine by default and shows up on the [API Tokens page](/console/access-tokens) in the Console, where you can revoke it anytime.

<Accordion title="Running in CI instead?">
  For automation that has no browser, the [GitHub Action](/github-action/get-started/getting-started) or any CI pipeline and use an account API key instead of `ironbee login`. Supply it through the environment:

  ```bash theme={null}
  export IRONBEE_API_KEY=<your-account-api-key>
  ```

  Find the account API key on the [Account page](/console/account) in the Console. See [Authentication](/cli/guides/authentication) for when to use each credential.
</Accordion>

***

## Step 4 - Set up your project

Navigate to your project directory and run:

```bash theme={null}
cd your-project
ironbee install
```

IronBee auto-detects your AI client and writes:

* **Hook configuration** — the client calls IronBee automatically when the agent finishes
* **Verification skill/rules** — the agent knows the verification workflow
* **MCP server entries** — `browser-devtools`, `node-devtools`, and `backend-devtools`
* **Permissions** — grants the agent access to devtools tools

<Info>
  If you are using **Cursor**, you need one extra step after install: go to **Settings → Tools & MCP** and confirm all three MCP servers (`browser-devtools`, `node-devtools`, `backend-devtools`) are enabled. See [Cursor setup](/cli/clients/cursor#activate-the-mcp-servers) for details.
</Info>

***

## Step 5 - Let the agent work

Open Claude Code, Cursor, or Codex and give the agent a task:

When the agent finishes editing code, IronBee intercepts the completion and requires verification:

1. The agent navigates to the affected pages in a real browser
2. It takes screenshots, checks the console, and tests functionality
3. It submits a verdict, pass or fail
4. If it fails, the agent fixes the issues and re-verifies

***

## Step 6 - View your results

Open the [IronBee Console](https://console.ironbee.ai) and navigate to your project. You will find:

* The session with all activity recorded
* Screenshots and browser interactions from each verification cycle
* Pass/fail verdict with evidence
* Timing breakdowns how long the agent spent coding, verifying, and fixing

***

## What's next?

<CardGroup cols={2}>
  <Card title="CLI configuration" icon="settings" href="/cli/configuration/configuration">
    Customize verify patterns, retry limits, and devtools settings.
  </Card>

  <Card title="Enable backend verification" icon="server" href="/cli/guides/verification#enable-or-disable-a-platform">
    Add Node.js or backend protocol verification for backend code changes.
  </Card>

  <Card title="GitHub Action" icon="git-branch" href="/github-action/get-started/getting-started">
    Verify changes automatically on every pull request.
  </Card>

  <Card title="Explore the console" icon="layout-dashboard" href="/console/projects">
    Understand sessions, verifications, findings, and recommendations.
  </Card>
</CardGroup>