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

# Quickstart: Set Up Your First AI Teammate

> Create your first AI teammate on Buckle Cloud, or self-host the stack with one command. Then grant it access to your tools and start delegating.

Two ways to run Buckle: the cloud at [buckle.dev](https://buckle.dev), or self-hosted on your own infrastructure. Either way, each person on your team gets an AI teammate that runs in its own sandbox, guarded by the gateway.

## Cloud-hosted

**1. Sign up**

Go to [buckle.dev](https://buckle.dev) and create your organization. A workspace is created for you automatically.

**2. Create an agent**

From the dashboard, create an agent. It gets its own sandbox, conversation page, memory, and skills.

**3. Grant a model key and connections**

Store an LLM key under **Settings** > **Apps** > **LLMs** (or use one shared by your organization), then **grant it to the agent**. The order matters: a sandbox will not start without a granted model key. Connect any services the agent should reach (Google, GitHub, Slack, AWS, and more) from the agent's **Apps** page, where a new connection is granted to that agent automatically. See [Agent access](/docs/guides/agent-access.md).

![The Apps page under Settings in the Buckle dashboard, with connected apps and the catalog](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/add-credentials.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=a0e4c2c444f4c9d706ef906891506b18)

**4. Start talking**

Chat with the agent from its dashboard page, or attach it to Slack so it answers in channels and DMs under its own name. Actions you flagged for approval show up as cards with Approve and Deny buttons, in the chat itself.

## Self-hosted

```bash theme={null}
git clone https://github.com/trybuckle/buckle.git && cd buckle
pnpm install
pnpm run setup
```

Open [localhost:10254](http://localhost:10254) and **create your account right away**. That account owns the instance; after it exists, joining needs an invitation.

No Node toolchain handy? The install script does the same without a clone:

```bash theme={null}
curl -fsSL https://buckle.dev/install | sh
```

Then follow the cloud steps above: create an agent, store a model key, grant it, and start talking. For raw Docker Compose, version pinning, and upgrades, see [Self-hosting](/docs/self-hosting/overview.md).

## Connect your own agent

Already running Claude Code, Cursor, or Codex? Route it through the gateway so it gets injected credentials without ever holding keys. Create a personal API key under **Settings** > **API keys**, then run:

```bash theme={null}
curl -fsSL buckle.dev/cli/install | sh
buckle auth login --api-key oc_your_api_key
buckle run -- claude
```

This wraps your agent with proxy settings, CA certificates, and agent skills automatically. Replace `claude` with `cursor`, `codex`, or any command. See the [Coding Agents guide](/docs/guides/coding-agents.md), or the [Node.js SDK](/docs/sdks/node.md) for Docker-based agents. To use your Claude plan, see [Claude setup-token](/docs/guides/claude-setup-token.md).

## Next steps

> [card] [Agent access](/docs/guides/agent-access.md)
>
> Grant each agent exactly the connections and secrets it needs.

> [card] [Integrations](/docs/integrations.md)
>
> Browse 40+ supported services and connect them from the dashboard.

> [card] [How it works](/docs/how-it-works.md)
>
> Architecture: gateway, runner, sandbox, and how the pieces fit together.

> [card] [Self-hosting](/docs/self-hosting/overview.md)
>
> Compose stack, version pinning, configuration, and upgrades.

## Troubleshooting

> [accordion] The agent says it has no model key
>
> Store the LLM key, then **grant it to the agent** from the key's Agent access dialog. A sandbox will not start without a granted model key.

> [accordion] OAuth redirect goes to the wrong URL (self-hosted / remote setups)
>
> If you're accessing a self-hosted Buckle through an SSH tunnel, reverse proxy, or on a remote server, OAuth callbacks may redirect to an unreachable address.
>
> Set `NEXT_PUBLIC_APP_URL` to the URL you actually use in your browser:
>
> ```bash theme={null}
> NEXT_PUBLIC_APP_URL=http://localhost:8080
> ```
>
> For SSH tunnel setups, forwarding to the same local port avoids this entirely:
>
> ```bash theme={null}
> ssh -L 10254:127.0.0.1:10254 user@host
> ```

> [accordion] Docker stack won't start (self-hosted)
>
> Make sure Docker is running and ports 10254/10255 are available. On every `docker compose up`, a one-shot `migrations` service applies pending database migrations before the API starts. If a migration fails, the stack refuses to start. Check `docker compose logs migrations`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.