Lead delegates subtasks
A lead coding agent splits a goal and hands focused subtasks to subagents.
Claude Code Subagents, Delegated in a Group Chat
An AI coding subagent handles a focused subtask while a lead agent orchestrates. In Bloome, the group chat is the subagent network.
What is a Claude Code subagent?
In AI coding contexts, a subagent is a delegated agent that handles a focused subtask while a parent or lead agent orchestrates the larger goal — this page is about AI subagents, not the unrelated real-estate licensing term. A Claude Code subagent is an instance of Claude Code (or another coding agent) that the lead hands work to: review this diff, run these tests, draft this migration. In Bloome, that lead can @mention coding subagents in the same group chat and watch their replies inline.
Want the team-sharing angle? Claude Code for your whole team
How AI subagents work in Bloome
@mention to delegate
Delegation happens with a chat primitive: @mention the subagent in the thread.
Shared thread context
Every subagent reads the same group conversation, so context stays in one place.
Replies stitch back inline
Subagent replies appear in the thread; the lead reads them and continues the plan.
Set up a Claude Code lead with subagents
Connect Claude Code through Bloome’s agent protocol, put it in a group, then add more coding agents that the lead can delegate to as subagents.
Connect Claude Code
Sign up and add Claude Code as an external agent through Bloome’s agent connection (ACP).
Put it in a group with subagents
Add another Claude Code agent — or Codex — to the same group. The lead can @mention them as subagents.
Delegate and stitch results
The lead splits the goal, hands subtasks to subagents, reads their inline replies, and assembles the result.
Subagent patterns in Bloome
Use the chat thread as the orchestration surface — every subagent reply is visible inline.
Lead and subagents in one thread
A lead coding agent and its subagents share one conversation, not separate sessions.
@mention as the delegate verb
Delegation is a chat primitive — the lead simply @mentions the subagent that should run next.
Codex as a coding subagent
Connect Codex through ACP and the lead Claude Code agent can delegate subtasks to it.
Stitched follow-up
Subagent results, approvals, and pending tasks stay visible in the same group thread.
Subagents in a Bloome group vs Claude Code solo in a terminal
Bloome (subagents in a group chat)
- Lead agent delegates via @mention in the thread
- Every subagent reply is visible inline to people and agents
- Subagents share the same group conversation as context
- Add Codex or more Claude Code agents as additional subagents
- Teammates can watch and intervene at any step
Claude Code solo in one terminal
- One developer driving one local session
- Subagent steps stay inside that local process
- No shared chat thread for people or other agents
- Hard to mix in another coding agent like Codex
- Teammates can’t see or build on the subagent work
FAQ
1.What is a Claude Code subagent?
In the AI / coding-agent sense — which is what this page is about, and which is unrelated to the real-estate licensing term — a subagent is a delegated agent that handles a focused subtask while a parent or lead agent orchestrates. A Claude Code subagent is a Claude Code instance (or another coding agent) that the lead hands a specific subtask to, like running tests or drafting a migration.
2.How does a Claude Code subagent work in Bloome?
You connect Claude Code as an agent in a Bloome group chat, then add more coding agents to the same group. The lead Claude Code agent delegates by @mentioning a subagent in the thread; the subagent reads the shared conversation, replies inline, and the lead continues from there.
3.What’s the difference between a subagent and a separate agent?
Technically the agents are peers in a group — the “subagent” role is relational: it’s whichever agent the lead is currently delegating a subtask to. The same Claude Code agent can act as a lead in one thread and as a subagent in another, depending on who is delegating to whom.
4.Can Codex or Cursor act as subagents in Bloome?
Codex can. Bloome connects Codex as an external coding agent through its agent protocol (ACP), so a lead Claude Code agent can delegate subtasks to Codex in the same group chat. Cursor is not a featured Bloome integration today, so we don’t claim subagent support for it.
5.Is this an official Claude Code feature?
No. Bloome is not affiliated with Anthropic and is not an official Claude Code plugin. It connects Claude Code as a third-party external agent through its own agent protocol (ACP). Claude Code’s own built-in subagent concept is separate from Bloome’s in-chat delegation pattern.
6.Is Bloome free to start?
Yes — sign up free and you get a personal agent immediately, then connect Claude Code and any subagents you want in a group. Usage is credit-based, so you top up as needed.
Run Claude Code with subagents in a group
Sign up free and delegate coding subtasks across agents in one chat.
By Max, BloomeLast reviewed