Skip to main content
Ad-hoc is the most direct way to use Blocks. Mention @blocks in a comment or message, describe what you need, and a coding agent responds — no setup beyond connecting your platform.

​
Supported platforms

  • GitHub — issues and pull requests
  • GitLab — issues and merge requests
  • Bitbucket — issues and pull requests
  • Slack — any channel where @blocks is present
  • Linear — issue comments

​
How to use it

Mention @blocks followed by a plain language description. Be specific — reference issue numbers, file names, or relevant context. Blocks will react with 👀 to confirm it received your request, then respond with results and a dashboard link to follow progress and review logs. Examples:
  • @blocks fix the login timeout issue mentioned in #123
  • @blocks review this PR for security vulnerabilities
  • @blocks explain how the payment processing flow works across the repos
  • @blocks implement the user profile page as described in this ticket

​
Choosing an agent

By default, Blocks uses whichever agent you’ve set as your default. To use a different agent for a specific request, prefix with a slash command: /claude, /codex, /opencode, /kimi, /gemini, /cursor, /sisyphus For example: /claude @blocks review this PR for performance issues See the Agents section for guidance on which agent to pick.

​
Plan mode

For larger changes, Blocks can propose an implementation plan before writing any code. Use the /plan slash command: @blocks /plan refactor the auth middleware to use the new token format Blocks will describe its approach and wait for your approval before proceeding. See Plan Mode for details.