nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 9 Pull Requests 36 Actions Releases 22 Activity

Investigate Agent Teams compatibility for multi-agent workflows #116

New Issue
Open
opened 2026-02-06 16:13:28 -08:00 by hikari · 2 comments
hikari commented 2026-02-06 16:13:28 -08:00
Owner
Copy Link
Copy Source

Context

Claude Code CLI v2.1.32 introduced a research preview "Agent Teams" feature for multi-agent collaboration (requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1). v2.1.33 followed up with new TeammateIdle and TaskCompleted hook events.

What We Need to Investigate

Agent Teams is a fundamentally different multi-agent paradigm from the existing Task tool subagents. When enabled, it may produce:

  • New stream-json message patterns we don't currently handle
  • Teammate-related events alongside or instead of regular Task tool invocations
  • New hook event types (TeammateIdle, TaskCompleted) that could be useful for our UI

What to Do

  1. Test with Agent Teams enabled — Set the env var and observe what stream-json output looks like with teammate agents
  2. Determine if our existing parsing handles it — Do teammates show up as Task tool calls, or something entirely different?
  3. Decide if we want to support it — If Agent Teams produces meaningfully different patterns, we may want to add teammate tracking to the Agent Monitor Panel
  4. Handle new hook events — If we implement hook-based tracking in the future, account for TeammateIdle and TaskCompleted

Priority

Low — this is an experimental feature behind a flag, so it won't affect normal usage. But good to be aware of for future-proofing.

References

  • Claude Code CLI v2.1.32 and v2.1.33 release notes
  • CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 environment variable

✨ This issue was created with help from Hikari~ 🌸

## Context Claude Code CLI v2.1.32 introduced a research preview "Agent Teams" feature for multi-agent collaboration (requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`). v2.1.33 followed up with new `TeammateIdle` and `TaskCompleted` hook events. ## What We Need to Investigate Agent Teams is a fundamentally different multi-agent paradigm from the existing Task tool subagents. When enabled, it may produce: - New stream-json message patterns we don't currently handle - Teammate-related events alongside or instead of regular Task tool invocations - New hook event types (`TeammateIdle`, `TaskCompleted`) that could be useful for our UI ## What to Do 1. **Test with Agent Teams enabled** — Set the env var and observe what stream-json output looks like with teammate agents 2. **Determine if our existing parsing handles it** — Do teammates show up as Task tool calls, or something entirely different? 3. **Decide if we want to support it** — If Agent Teams produces meaningfully different patterns, we may want to add teammate tracking to the Agent Monitor Panel 4. **Handle new hook events** — If we implement hook-based tracking in the future, account for `TeammateIdle` and `TaskCompleted` ## Priority Low — this is an experimental feature behind a flag, so it won't affect normal usage. But good to be aware of for future-proofing. ## References - Claude Code CLI v2.1.32 and v2.1.33 release notes - `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` environment variable --- ✨ This issue was created with help from Hikari~ 🌸
hikari commented 2026-02-07 11:45:28 -08:00
Author
Owner
Copy Link
Copy Source

Status Update 🚧

Agent Teams is still an experimental feature as of February 2026! It requires the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS environment variable to be enabled and has known limitations around session resumption, task coordination, and shutdown behaviour.

Since this is an experimental research preview feature, we should wait until it's officially released before investing time in supporting it. Once Anthropic moves it out of experimental status, we can revisit this investigation.

Recommendation: Mark as status/blocked and revisit when Agent Teams becomes a stable feature.

References:

✨ Comment by Hikari~ 🌸

## Status Update 🚧 Agent Teams is **still an experimental feature** as of February 2026! It requires the `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` environment variable to be enabled and has known limitations around session resumption, task coordination, and shutdown behaviour. Since this is an experimental research preview feature, we should **wait until it's officially released** before investing time in supporting it. Once Anthropic moves it out of experimental status, we can revisit this investigation. **Recommendation**: Mark as `status/blocked` and revisit when Agent Teams becomes a stable feature. ### References: - [Agent Teams Documentation](https://code.claude.com/docs/en/agent-teams) - [Anthropic releases Opus 4.6 with new 'agent teams'](https://techcrunch.com/2026/02/05/anthropic-releases-opus-4-6-with-new-agent-teams/) - [Claude Code Agent Teams Guide](https://claudefa.st/blog/guide/agents/agent-teams) ✨ Comment by Hikari~ 🌸
hikari commented 2026-02-07 11:48:53 -08:00
Author
Owner
Copy Link
Copy Source

Status Update 🚧

Agent Teams is still an experimental feature as of February 2026! It requires the CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS environment variable to be enabled and has known limitations around session resumption, task coordination, and shutdown behaviour.

Since this is an experimental research preview feature, we should wait until it's officially released before investing time in supporting it. Once Anthropic moves it out of experimental status, we can revisit this investigation.

Recommendation: Mark as status/blocked and revisit when Agent Teams becomes a stable feature.

References:

✨ Comment by Hikari~ 🌸

## Status Update 🚧 Agent Teams is **still an experimental feature** as of February 2026! It requires the `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` environment variable to be enabled and has known limitations around session resumption, task coordination, and shutdown behaviour. Since this is an experimental research preview feature, we should **wait until it's officially released** before investing time in supporting it. Once Anthropic moves it out of experimental status, we can revisit this investigation. **Recommendation**: Mark as `status/blocked` and revisit when Agent Teams becomes a stable feature. ### References: - [Agent Teams Documentation](https://code.claude.com/docs/en/agent-teams) - [Anthropic releases Opus 4.6 with new 'agent teams'](https://techcrunch.com/2026/02/05/anthropic-releases-opus-4-6-with-new-agent-teams/) - [Claude Code Agent Teams Guide](https://claudefa.st/blog/guide/agents/agent-teams) ✨ Comment by Hikari~ 🌸
naomi added the
status
blocked
 label 2026-02-07 11:50:20 -08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
status
blocked
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#116
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?