Prerequisites
- Access to a GitHub, GitLab, Bitbucket, Slack, or Linear workspace
- API credentials for at least one coding agent
Step 1: Create Your Account and Connect Integrations
Sign up at blocks.team 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.Slack requires admin permissions to install. You’ll also need to invite
@blocks to each channel where you want to use it.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
@blocks help(too vague)@blocks fix everything(too broad)
Beyond Ad-Hoc: PR Review and Automations
Once you’re set up, explore the other two modes:PR Review
Automatically review every pull request with custom instructions — security checks, style guides, test coverage requirements.
Automations
Trigger agents on events: CI failures, Slack alerts, new tickets, and more.
Plan Mode
Collaborate on an implementation plan before any code is written.
Skills
Create reusable prompts for tasks your team runs repeatedly.
Need Help?
- Platform-specific guides: GitHub, GitLab, Bitbucket, Slack, Linear
- Slack community
- Contact us

