Key takeaways
- Blocks integrates coding agents (Claude Code, Codex, OpenCode, Gemini CLI, Cursor CLI) into GitHub, Slack, and Linear via @blocks mentions
- Agent-agnostic — lets teams choose and switch between multiple coding agents per task
- Custom agents via Blocks SDK using Python, with support for smolagents and LiteLLM
- Currently in beta and free for early users; pricing TBA before GA
FAQ
What is Blocks?
Blocks is a platform that brings coding agents into your team's existing workflow tools (GitHub, Slack, Linear) via @blocks mentions, letting you use Claude Code, Codex, OpenCode, and other agents without switching contexts.
How much does Blocks cost?
Blocks is currently in beta and free for early users with limited quotas. Pricing will be announced before general availability.
What agents does Blocks support?
Stable agents include Claude Code and Codex. Experimental agents include OpenCode, Sisyphus (multi-agent), Gemini CLI, and Cursor CLI.
Who competes with Blocks?
Tembo, Devin, Factory, and 8090 compete in the agent orchestration and workflow integration space.
Executive Summary
Blocks is a workflow-integration platform that brings coding agents into the tools teams already use — GitHub, Slack, and Linear. Rather than building its own agent, Blocks orchestrates existing ones (Claude Code, Codex, OpenCode, and more) and lets teams invoke them via simple @mentions. Currently in beta with free access for early users. [1]
| Attribute | Value |
|---|---|
| Company | Blocks |
| Founded | Unknown |
| Funding | Not disclosed |
| Headquarters | Unknown |
Product Overview
Blocks positions itself as a workflow-first agent platform — rather than replacing your dev tools, it embeds coding agents inside them. Mention @blocks in a GitHub issue, Slack thread, or Linear ticket, and a coding agent of your choice picks up the task. [2]
The key differentiator is agent choice: teams aren't locked to a single AI. Claude Code handles most tasks well, Codex brings deep reasoning, OpenCode offers privacy-focused open-source, and Sisyphus provides multi-agent orchestration for complex workflows.
Key Capabilities
| Capability | Description |
|---|---|
| Multi-Agent Support | Claude Code, Codex, OpenCode, Sisyphus, Gemini CLI, Cursor CLI |
| @mentions Integration | Invoke agents from GitHub, Slack, or Linear |
| Multi-Repo | Work across multiple repositories simultaneously |
| Plan Mode | Collaborate on implementation plans before code changes |
| Custom Commands | Reusable prompts and workflows for common tasks |
| Custom Agents (SDK) | Build custom agents in Python using Blocks SDK + smolagents/LiteLLM |
Product Surfaces / Editions
| Surface | Description | Availability |
|---|---|---|
| GitHub | PR review, address comments, issue-to-PR | Beta |
| Slack | Unblock team members, delegate tasks, create tickets | Beta |
| Linear | Assign tickets, improve requirements, status updates | Beta |
| Dashboard | Web UI for tracking agent progress | Beta |
Technical Architecture
Blocks runs agents in serverless remote environments — no infrastructure to manage. When invoked via @mention, Blocks:
- Detects the context (repo, issue, PR, thread)
- Spins up the selected coding agent in an isolated environment
- Provides real-time progress updates
- Delivers results (PRs, comments, answers) back to the source tool
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | Cloud-based (serverless) |
| Agent Runtime | Remote sandboxed environments per agent |
| Integrations | GitHub, Slack, Linear (OAuth) |
| Open Source | No (SDK available for custom agents) |
| Auth | Anthropic subscription or API keys |
Strengths
- Workflow-native — Meets teams where they work (GitHub, Slack, Linear) instead of adding another tool
- Agent-agnostic — Choose the best agent per task; not locked to one provider
- Low friction — @mention interface requires zero context-switching
- Multi-repo support — Agents understand cross-repository context
- Custom SDK — Build custom agents with Python, smolagents, and LiteLLM
- BYOS (Bring Your Own Subscription) — Uses existing Claude/Codex subscriptions
Cautions
- Beta stage — Product is pre-GA with limited quotas; stability uncertain
- No local development — Cloud-only, no CLI or local agent support
- No automations — No scheduled (cron) or event-triggered agent runs
- Pricing unknown — Free during beta, but no pricing announced
- Limited visibility — No disclosed funding, team size, or traction metrics
- No enterprise features — No SSO, SOC2, audit logs, or compliance certifications mentioned
- Privacy concerns — Data deletion configurable but "no training" policy details sparse
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Beta | Free | Limited quotas |
| GA | TBA | Individual and team plans planned |
Licensing model: Freemium (anticipated)
Hidden costs: Requires Anthropic subscription for Claude Code, or API keys for other agents
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| Tembo | Tembo orchestrates CLI agents with cron/event automations and 11 integrations; Blocks focuses on @mention workflow integration |
| Devin | Devin is a single proprietary agent; Blocks lets you choose from multiple agents |
| Factory | Factory has enterprise Droids with compliance; Blocks is lighter-weight and agent-agnostic |
| 8090 | 8090 captures requirements upstream; Blocks focuses on execution in existing tools |
When to Choose Blocks Over Alternatives
- Choose Blocks when: You want to use familiar agents (Claude Code, Codex) directly from GitHub/Slack/Linear without another dashboard
- Choose Tembo when: You need automation (cron, events), deep integrations (databases, Sentry), and CLI agent orchestration
- Choose Devin when: You want a fully autonomous AI engineer for junior-level tasks at scale
- Choose Factory when: You need enterprise compliance, SSO, and audit trails
Ideal Customer Profile
Best fit:
- Teams heavily using GitHub, Slack, and Linear for development workflow
- Organizations wanting agent flexibility without building infrastructure
- Developers who want to try multiple coding agents without switching tools
- PMs and non-engineers who want to delegate technical tasks via Slack/Linear
Poor fit:
- Teams needing automated/scheduled agent runs
- Organizations requiring enterprise compliance (SOC2, SSO)
- Developers wanting local/CLI-first workflows
- Companies needing database integrations or deep observability
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | Unknown — no disclosed funding |
| Market Position | Early — beta stage, building initial user base |
| Innovation Pace | Active — multiple experimental agents, SDK released |
| Community/Ecosystem | Nascent — Reddit presence, early adopters |
| Long-term Outlook | Uncertain — depends on funding and GA execution |
Blocks occupies an interesting niche: workflow-native agent orchestration. The @mention paradigm is intuitive and reduces adoption friction. However, the lack of disclosed funding, enterprise features, and automation capabilities limits near-term competitiveness against funded players like Tembo, Factory, and Devin.
Bottom Line
Blocks brings coding agents to where teams already work — GitHub, Slack, and Linear. The agent-agnostic, @mention-driven approach is compelling for teams wanting AI assistance without adding another tool to their stack.
Recommended for: Teams using GitHub/Slack/Linear who want to experiment with multiple coding agents through a unified @mention interface.
Not recommended for: Teams needing enterprise compliance, automated agent runs, database integrations, or local development support.
Outlook: Blocks needs to ship GA pricing, prove reliability at scale, and add automation capabilities to compete with better-funded orchestration platforms. The workflow-native positioning is strong, but execution and funding will determine whether it becomes a category leader or a feature that larger platforms absorb.
Research by Ry Walker Research • methodology