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

# Getting Started

> Set up Blocks and make your first request

## Prerequisites

* Access to a GitHub, GitLab, Bitbucket, Slack, or Linear workspace
* API credentials for at least one coding agent

<Tip>Start with **Claude Code** — it's the most capable agent for general tasks and requires only an [Anthropic API key](https://console.anthropic.com/).</Tip>

## Step 1: Create Your Account and Connect Integrations

[Sign up at blocks.team](https://blocks.team/signup) and follow the onboarding. It will walk you through connecting your platforms and configuring your first coding agent.

You can add or update integrations at any time from **Settings → Integrations**.

<Note>Slack requires admin permissions to install. You'll also need to invite `@blocks` to each channel where you want to use it.</Note>

## Step 2: Set Your Default Agent

Only Claude Code, Codex, and OpenCode can be set as the default agent. Gemini CLI, Cursor CLI, and Sisyphus must be invoked explicitly with slash commands (`/gemini`, `/cursor`, `/sisyphus`).

To change your default: **Dashboard → Agents → Set as default agent**.

You can always override per-request with `/claude`, `/codex`, `/opencode`, or `/kimi`.

## Step 3: Make Your First Request

Mention `@blocks` in any issue, PR comment, Slack message, or Linear ticket and describe what you need in plain language. Be specific — reference issue numbers, file names, or relevant context.

Good requests:

* `@blocks fix the login timeout issue mentioned in #123`
* `@blocks review this PR for performance issues`
* `@blocks explain how the payment processing flow works`

Less effective:

* `@blocks help` (too vague)
* `@blocks fix everything` (too broad)

Blocks will react with 👀 to confirm it received your request, then reply with results and a dashboard link where you can follow progress and review logs.

## Beyond Ad-Hoc: PR Review and Automations

Once you're set up, explore the other two modes:

<CardGroup cols={2}>
  <Card title="PR Review" icon="git-pull-request" href="/using-blocks/products/pr-review">
    Automatically review every pull request with custom instructions — security checks, style guides, test coverage requirements.
  </Card>

  <Card title="Automations" icon="zap" href="/using-blocks/products/automations">
    Trigger agents on events: CI failures, Slack alerts, new tickets, and more.
  </Card>

  <Card title="Plan Mode" icon="clipboard-list" href="/using-blocks/features/plan-mode">
    Collaborate on an implementation plan before any code is written.
  </Card>

  <Card title="Skills" icon="terminal" href="/using-blocks/features/skills">
    Create reusable prompts for tasks your team runs repeatedly.
  </Card>
</CardGroup>

## Need Help?

* Platform-specific guides: [GitHub](/using-blocks/integrations/github), [GitLab](/using-blocks/integrations/gitlab), [Bitbucket](/using-blocks/integrations/bitbucket), [Slack](/using-blocks/integrations/slack), [Linear](/using-blocks/integrations/linear)
* [Slack community](/using-blocks/support/community)
* [Contact us](/using-blocks/support/contact)