Team Agent Platforms

Related: For individual AI assistants (email, calendar, personal productivity), see Personal Agents Platforms Compared.

Executive Summary

Team agent platforms deploy shared AI agents that entire teams can access via Slack, Discord, or APIs. Unlike personal AI assistants (managing your email and calendar) or local IDE tools (your personal Cursor or Copilot), these platforms enable collaborative, asynchronous workflows across functions — from product planning and coding to data analysis and customer support.

Key Findings:

• Claude leads in breadth — Claude's cowork capabilities in Slack span product planning, research, coding, writing, and cross-functional collaboration — the widest capability set
• Coding specialists emerge — Codex, Kilo, Devin, and Tembo focus specifically on development workflows with deep GitHub/Linear integrations
• Non-engineers as users — Claude cowork, eksec, Tasklet, and Viktor explicitly target non-technical team members
• Orchestration layer emerges — Tembo, eksec, and CrewAI let teams use multiple agent backends while providing unified interfaces

Strategic Planning Assumptions:

• By 2027, 60% of teams will have a shared agent accessible via team chat
• By 2026 year-end, at least two major companies will mandate team agent usage for routine tasks
• By 2028, orchestration platforms will capture 40% of the market as teams resist single-vendor lock-in

---

Market Definition

Team agent platforms deploy shared AI agents accessible across teams. Unlike personal agents (managing your individual email and calendar) or local IDE tools (your personal Cursor or Copilot), these agents are:

• Shared — Accessible by multiple team members across functions
• Asynchronous — Work continues without user presence
• Integrated — Live in Slack, Discord, or existing collaboration tools
• Action-oriented — Create PRs, draft documents, analyze data, execute workflows

Inclusion Criteria:

• Deploys agents accessible via team chat (Slack, Discord, Teams)
• Shared across multiple team members (not individual-only)
• Can take action (code, documents, data, operations)
• Operates asynchronously (not just real-time chat)

Exclusion Criteria:

• Personal AI assistants (Lindy, Manus, OpenClaw) — individual-focused
• Local IDE tools (Cursor, Copilot, Windsurf) — not team-shared by default
• Pure frameworks (LangChain, AutoGen) — require significant integration
• Chatbots without action capability

---

Comparison Matrix

Platform	Backend	Slack	Discord	Open Source	Pricing	Maturity
Agentforce	Salesforce	✅	—	—	Enterprise	GA
Claude in Slack	Claude	✅	—	—	Pro/Team/Ent	GA
Codex in Slack	OpenAI	✅	—	—	Plus/Pro/Ent	GA
Composio	Any (infra)	—	—	✅	Free tier	GA
CrewAI Enterprise	Any	✅	—	Partial	$25+/mo	GA
Devin	Proprietary	✅	—	—	$500/mo	GA
eksec.ai	Claude/Codex/OpenCode	✅	✅	—	Free tier	Beta
Kilo for Slack	Any (500+ models)	✅	—	✅	Pay-as-go	GA
Runbear	OpenAI/Claude	✅	✅	—	$15+/mo	GA
Spacebot	Any	✅	✅	✅	Free–$129/mo	GA
Tasklet	Claude	—	—	—	$35/mo	GA
Tembo	Claude/Codex/Cursor	✅	—	—	Contact	GA
Tensol	OpenClaw	✅	—	—	Contact	Beta
Viktor	Proprietary	✅	—	—	$99–999/mo	GA

---

Capabilities Matrix

Team agents vary widely in what they can do. This matrix rates each platform across six capability areas:

Platform	Product Planning	Coding	Data Analysis	Customer Support	Sales/CRM	Operations
Agentforce	—	—	✅	✅	✅	✅
Claude in Slack	✅	✅	✅	✅	—	—
Codex in Slack	—	✅	—	—	—	—
Composio	—	✅	✅	—	✅	✅
CrewAI Enterprise	—	—	—	—	—	—
Devin	—	✅	—	—	—	—
eksec.ai	—	✅	✅	—	—	—
Kilo for Slack	—	✅	—	—	—	—
Runbear	—	—	—	✅	✅	✅
Spacebot	—	✅	—	—	—	—
Tasklet	—	—	—	—	—	✅
Tembo	—	✅	—	—	—	—
Tensol	—	✅	—	—	—	✅
Viktor	—	✅	✅	—	—	✅

✅ = Strong | — = Limited/None

Capability Definitions:

• Product Planning — PRDs, specs, requirements gathering, roadmap collaboration
• Coding — Write code, create PRs, fix bugs, refactor, code review
• Data Analysis — Query databases, generate reports, analyze metrics
• Customer Support — Answer tickets, route requests, knowledge base queries
• Sales/CRM — Pipeline updates, lead research, account management
• Operations — Workflow automation, scheduling, cross-team coordination

Key Insight: Claude in Slack (with cowork mode) is the only platform with strong capabilities across all six areas. Coding-focused platforms (Codex, Kilo, Devin, Tembo) excel at development but lack broader business capabilities. Agentforce and Runbear are strong in support/sales but weak in coding.

---

Platform Profiles

Agentforce

Salesforce's enterprise AI agents in Slack — CRM-focused, not coding-focused

• Deep Salesforce integration — Full access to CRM data and existing workflows
• Pre-built skills — Sales, service, marketing, IT, finance templates
• Visual builder — Drag-and-drop agent creation
• Enterprise-only — Requires Salesforce investment; complex pricing

Best For: Salesforce-centric enterprises needing business workflow automation.

---

Claude in Slack

Anthropic's native Slack integration — broadest capabilities from coding to product planning

• Cowork mode — Product planning, research, writing, and cross-functional collaboration
• Claude Code mode — Full coding capabilities with PR creation and code review
• Thread context — Gathers context from entire Slack threads
• Team visibility — Progress visible to entire channel; seamless web handoff
• Claude-only — No multi-model support; $25-150/user/mo

Best For: Teams wanting broadest capability set — the only platform strong across all six capability areas.

---

Codex in Slack

OpenAI's native Slack integration — tag @Codex to kick off cloud tasks

• Auto environment selection — Picks the right repo from context
• Full thread history — References earlier messages automatically
• Enterprise controls — Admins can restrict answer posting
• OpenAI-only — ChatGPT Plus/Pro/Enterprise required

Best For: Teams standardized on OpenAI wanting native Slack experience.

---

Composio

Open source agent integration layer — 1000+ toolkits, managed auth, 27K GitHub stars

• 1000+ toolkits — GitHub, Slack, Salesforce, databases, and more out of the box
• Framework-agnostic — Works with OpenAI, Anthropic, LangChain, CrewAI, AutoGen
• Managed auth — OAuth2, API keys, and token refresh handled automatically
• YC W24 — $29M funding (July 2025); strong traction
• Infrastructure layer — Powers agents, not a Slack bot itself

Best For: Teams building custom agents that need to connect to multiple SaaS tools and APIs.

---

CrewAI Enterprise

Multi-agent orchestration with visual editor — 29K+ GitHub stars

• Multi-agent workflows — Agents collaborate with role-based specialization
• Visual editor — Build crews without code
• Open source core — Apache 2.0 licensed
• Broad integrations — Gmail, Teams, Slack, Notion, HubSpot, Salesforce

Best For: Teams wanting multi-agent patterns with open source foundation.

---

Devin

Fully autonomous AI engineer with own IDE — $175M funding from Cognition Labs

• Full autonomy — Plans, codes, tests, submits PRs without intervention
• Own environment — Dedicated IDE, shell, browser; no setup
• Voice input — Accept voice tasks via Slack (Devin 1.2)
• Premium pricing — $500/mo Teams; proprietary models only

Best For: Teams wanting maximum autonomy and willing to pay premium. Tembo competes directly with agent-agnostic orchestration.

---

eksec.ai

Team agent orchestration — deploy Claude Code, OpenCode, or Codex via Slack/Discord

• Multi-backend — Choose Claude Code, OpenCode, or Codex
• Discord support — One of few platforms with Discord
• Non-technical focus — PMs and ops can query DBs, submit PRs
• Beta stage — Limited track record; pricing unclear

Best For: Teams wanting model flexibility with Discord support.

---

Kilo for Slack

Open source coding agent — 1.5M+ users, 500+ models, pay-as-you-go

• Model flexibility — 500+ models; no vendor lock-in
• Fully open source — Apache 2.0; inspect and modify
• Massive community — 1.5M+ users; #1 on OpenRouter
• Pay-as-you-go — No subscription; exact API prices

Best For: Teams wanting open source with model flexibility and cost control.

---

Runbear

No-code AI agent builder — 300K users, 2000+ integrations

• No-code builder — Create agents without programming
• Multi-platform — Slack, Teams, Discord, HubSpot
• 2000+ integrations — Connect virtually any tool
• Ops-focused — Better for Q&A and routing than coding

Best For: Ops teams wanting no-code agents across multiple platforms.

---

Spacebot

Open source multi-agent from Spacedrive — 12K stars, Discord/Slack native

• Multi-agent architecture — Channel → Branch → Worker (nothing blocks)
• Open source — Full source, self-host option
• Graph memory — 8 typed memory kinds
• Community-focused — Less enterprise-oriented

Best For: Discord-first communities wanting open source multi-agent.

---

Tasklet

Plain-English automation from Firebase co-founder — describe processes, AI executes

• No workflow builder — Describe in English; AI figures out implementation
• Firebase team — Andrew Lee, USV + Lightspeed backed
• Flexible triggers — Scheduled, email, webhooks
• Not Slack-native — Posts to Slack but no @mention interface

Best For: Business process automation; not specifically for coding workflows.

---

Tembo

Coding agent orchestration — any agent, from Slack, Linear, or GitHub

• Multi-agent — Claude Code, Codex, Cursor, Amp, OpenCode
• Multi-repo PRs — Single tasks across multiple repositories
• Multiple surfaces — Slack, Linear, GitHub, Jira
• TypeScript SDK — Use Tembo as tool call in your own agents

Best For: Teams wanting model flexibility with unified orchestration.

---

Tensol

Managed OpenClaw for B2B — VM isolation, OAuth, audit logs (YC W26)

• 5-minute setup — No infrastructure to manage
• Per-customer isolation — VM-level separation for enterprise
• Enterprise features — OAuth, audit logs, SSO
• Early stage — 2-person team; still proving product-market fit

Best For: Teams wanting managed OpenClaw with enterprise security.

---

Viktor

Slack-native agent with persistent compute — 3,000+ integrations

• Own compute — Persistent cloud environment for code execution
• 3,000+ integrations — Browser automation + native APIs
• Slack-native — Joins channels, maintains context
• Credit-based — $99-999/mo depending on usage

Best For: Teams wanting Slack-native agent with autonomous compute.

---

Architecture Patterns

First-Party vs. Orchestration

Approach	Examples	Pros	Cons
First-party	Claude Code in Slack, Codex in Slack	Seamless integration, native experience	Single-vendor lock-in
Orchestration	Tembo, eksec, Kilo	Model flexibility, unified interface	Extra layer, setup complexity
Autonomous	Devin	Full environment, maximum autonomy	Higher cost, less transparency
Framework	CrewAI	Maximum customization	Requires development effort
Infrastructure	Composio	1000+ integrations, managed auth	Not a direct agent; enables others

Slack-First vs. Multi-Channel

Most platforms prioritize Slack, reflecting its dominance in engineering teams:

Platform	Slack	Discord	Teams	API
Claude Code	✅	—	—	✅
Codex	✅	—	—	✅
Composio	—	—	—	✅
Devin	✅	—	✅	✅
eksec	✅	✅	—	✅
Kilo	✅	—	—	✅
Runbear	✅	✅	✅	✅
Spacebot	✅	✅	—	✅
Tasklet	—	—	—	✅
Tembo	✅	—	—	✅
Viktor	✅	—	—	✅

---

Gap Analysis

Feature	Claude Slack	Codex Slack	Composio	Devin	eksec	Kilo	Spacebot	Tasklet	Tembo	Viktor
Multi-model support	—	—	✅	—	✅	✅	✅	—	✅	—
Multi-repo PRs	—	—	—	✅	—	—	—	—	✅	—
Discord support	—	—	—	—	✅	—	✅	—	—	—
Open source	—	—	✅	—	—	✅	✅	—	—	—
Voice input	—	—	—	✅	—	—	—	—	—	—
Non-tech user focus	—	—	—	—	✅	—	—	✅	✅	✅
Enterprise SSO	✅	✅	—	✅	?	—	—	—	✅	?
Self-hosted option	—	—	—	—	—	✅	✅	—	✅	—

Key gaps across the market:

• Discord support limited — eksec, Runbear, and Spacebot; Discord-first teams underserved
• Multi-model mostly orchestration — First-party integrations don't allow model switching
• Open source options growing — Kilo, CrewAI, and Spacebot; still mostly proprietary
• Voice input rare — Only Devin 1.2 supports voice messages via Slack

---

Strategic Recommendations

By Use Case

Use Case	Recommended	Runner-Up
Single-vendor Claude shop	Claude Code in Slack	—
Single-vendor OpenAI shop	Codex in Slack	—
Model flexibility needed	Tembo	Kilo
Non-technical users	eksec	Tembo
Enterprise with Salesforce	Agentforce	—
Open source requirement	Kilo	Spacebot
Discord/community teams	Spacebot	eksec
Slack-native with compute	Viktor	Devin
Discord-based team	eksec	Runbear
Maximum autonomy	Devin	—
Budget-conscious	Kilo (pay-as-go)	Runbear ($15/mo)
Business process automation	Tasklet	Runbear
Building custom agents	Composio	CrewAI

By Buyer Profile

Startups (< 20 engineers): → Start with Claude Code or Codex in Slack if already on those models. Consider Kilo for cost control with pay-as-you-go pricing.

Scale-ups (20-200 engineers): → Tembo or eksec for multi-agent flexibility. The orchestration layer pays off as team preferences diverge and you want unified interfaces.

Enterprise (200+ engineers): → Evaluate Devin for high-autonomy needs, Agentforce if Salesforce-centric. First-party integrations (Claude/Codex) work well for standardized tool stacks.

Open Source-First Teams: → Kilo is the clear choice — fully open source, 1.5M+ users, pay-as-you-go. CrewAI if you need multi-agent orchestration patterns.

---

Market Outlook

Near-Term (2026)

• Claude Code and Codex Slack integrations will exit beta and add enterprise features
• Tembo and eksec will compete for the "orchestration layer" positioning
• At least one major acquisition in this space (watch Kilo, backed by GitLab co-founder)

Medium-Term (2027-2028)

• 60% of engineering teams will have a shared coding agent
• Discord support will become standard as gaming/crypto teams adopt
• Voice-first interfaces (like Devin 1.2) will expand across platforms

Long-Term (2029+)

• Team agents will be default infrastructure, like CI/CD
• Orchestration platforms will dominate as teams resist single-vendor lock-in
• The distinction between "team agent" and "autonomous engineer" will blur

---

Bottom Line

Team agent platforms are rapidly maturing from experimental tools to essential infrastructure. The market is splitting into three camps:

Current Leaders:

• Claude Code in Slack for Anthropic-standardized teams
• Codex in Slack for OpenAI-standardized teams
• Devin for maximum autonomy (at premium pricing)

Rising Challengers:

• Tembo for multi-agent orchestration with enterprise focus
• Kilo for open source flexibility and cost control

The key strategic question: Do you want model lock-in for seamless experience (Claude/Codex), or orchestration flexibility at the cost of an extra layer (Tembo/Kilo/eksec)?

For most teams, the answer will evolve. Start with first-party integrations if you're standardized on one model. Move to orchestration as team needs diversify and you want unified interfaces across agents.

---

Research by Ry Walker Research • methodology

Disclosure: Author is CEO of Tembo, which competes in this category.