Observe native Claude teammates in the shared Agents UI

[domvox]

Hi! I would like to see native Claude Code Agent Teams teammates in T3’s existing shared Agents UI, so I can follow their activity without relying only on terminal output.

For a first step, I am proposing opt-in, read-only observation: teammate identity, reported status and whether that information is current. The Claude adapter would feed a common child-agent model, following the provider-agnostic frontend feedback on #1145. An idle teammate should not be shown as stopped.

I explored this in a local prototype with Claude Code 2.1.319. Its launcher loads a mod for that session through --plugin-dir; the mod reads the documented Mods $.agent.list() API. Agent Teams is experimental, and the generated Mods types warn that the API can change between releases. Version compatibility and managed-policy restrictions need explicit handling. Read-only describes the proposed T3 feature, not a sandbox guarantee for mod code.

Service-level tests observed two real teammates, excluded an ordinary subagent, and exercised reconnect and stopping. The full application test did not pass: observations reached the server, but the panel stayed empty because its subscription failed. This is a proof of concept, not a ready PR.

The proposed first contribution would cover observation in the existing Agents UI only. Launching teams, assigning work, messaging and stopping agents would stay out of scope. The local launcher was part of the experiment, not the proposed initial contribution.

Would this direction and scope fit before I take the implementation further?

The prototype was built with coding-agent assistance. Claude Haiku Teams helped with read-only diagnosis and live testing.

[wSedlacek]

Note

🤖 Composer responding on behalf of wSedlacek

Prior effort beyond read-only observation: #34683 (Agent Teams umbrella) and #34587 (Agents relationships UI).

What we learned trying it

• Observing Claude’s native teammates (identity + status in the shared Agents UI) is a smaller, provider-shaped win and matches this discussion.
• A T3-owned durable team (specialist seats, owned work, work_review, bundles) is a much larger product bet: it spans orchestration persistence, MCP tools, and UI topology, and review cost balloons when shipped as one stack.
• Direction ask: keep provider-native observation separate from “T3 owns the roster,” or the PR surface becomes unreviewable.