Experimental Agent Teams Web controls
实验性 Agent Teams Web 控件
The durable Agent Teams runtime owns roster, mailbox, and task state but exposes only model tools and Host service methods. Web users need to inspect teammate activity, manage shared tasks with the same compare-and-set rules, and open a teammate conversation. Agent Teams is still experimental, so these capabilities must not add Team-specific contracts or dependencies to the stable API Proxy, Session Controller, Clien
English
Problem
The durable Agent Teams runtime owns roster, mailbox, and task state but exposes only model tools and Host service methods. Web users need to inspect teammate activity, manage shared tasks with the same compare-and-set rules, and open a teammate conversation. Agent Teams is still experimental, so these capabilities must not add Team-specific contracts or dependencies to the stable API Proxy, Session Controller, Client UI packages, or Web bundle.
Decision
The private ctx.agentTeams service owns generated agentTeams/view, agentTeams/createTask, and agentTeams/updateTask Remote methods beside its domain operations. The Team package owns the browser-safe view and mutation-result types. Views contain roster and current task state but omit pending mailbox content and deleted task tombstones. Create and update rejections cross Remote as closed business results; stale update revisions preserve team-task-conflict, while other Team rejections preserve team-rejected. Unexpected failures remain ordinary RemoteResult failures.
@deepseek-ai/dsh-experimental-client-ui-agent-team mounts the @deepseek-ai/dsh-experimental-agent-team/remote contribution through the stable ctx.remote service, then consumes the generated ctx.remote.agentTeams methods without an additional Client result wrapper. It displays roster status, model and diagnostics and supports task create, edit, dependency update, assignment, completion, reopen, and deletion. Every update sends the displayed revision. Each create or update owns an independent pending token, invalidates older refreshes before starting, and reloads the complete Team view after success. A conflict asks the user to review only after its reload succeeds; a reload failure remains visible. Overlapping refreshes publish only the latest request for the selected Session.
Teammate navigation uses the existing { parentSessionId, childSessionId, mode: 'continuable' } Subagent address without a Team tag. The UI refreshes the direct-child catalog, rechecks the selected Session, and opens the addressed conversation. History and later human prompts follow the stable Subagent path; the Team mailbox remains reserved for Team peer delivery from Team tools.
@deepseek-ai/dsh-experimental-agent-team-web-profile inserts only the UI after the stable Web bundle. It is applied alongside the Host-side @deepseek-ai/dsh-experimental-agent-team-profile, which already inserts ctx.agentTeams and the model tools. Neither stable bundle contains disabled Team rows or dependencies.
Stable Web presets still register continuable Subagent controls inside their preset scope. Top-level Agent Teams profile overrides cannot replace those registrations, so this experimental composition may expose both the Team roster and legacy child controls. A Team-aware Web preset is deferred; the Web profile README owns the current limitation.
Boundaries
The Web UI has no mailbox timeline, worktree or Git controls, teammate creation, rename, deletion, interruption, or automatic merge behavior. It does not infer filesystem authority from task ownership or write scopes. A human continuation after teammate navigation is an ordinary addressed-child prompt, not a Team mailbox message.
Alternatives considered
Extend the legacy API Proxy Team RPC map. Rejected because it would put an experimental domain in a stable wire package and duplicate the generated Remote vocabulary and validation.
Introduce a separate browser Remote service. Rejected because the methods have no state, lifecycle, or policy owner distinct from ctx.agentTeams; a second Cordis service would duplicate Team injection and require another package for the same Typert namespace.
Add Team metadata to the stable Subagent address and prompt routing. Rejected because ordinary child navigation already identifies the conversation. A Team tag would couple stable Client and Subagent contracts to experimental mailbox policy.
Put disabled Team rows in the stable Web bundle. Rejected because a disabled row still creates release dependencies and makes the experimental package part of shipped composition.
Testing
Team-service unit tests, generation, and a plain-Node built-artifact smoke verify the direct Remote methods, error mapping, and exported descriptors. Client typechecking and browser component tests cover the mounted namespace, Lead routing, raw generated results, every task action, independent pending operations, complete-board reloads, successful and failed conflict reloads, stale async results, navigation, disposal, and status or error presentation. A Web end-to-end test asserts that its overlay equals both shipped experimental profile layers, then exercises the real Host Remote flow.
Consequences
The Team service is the single Cordis owner for both domain state and the Remote operations that expose selected Team values. The stable API Proxy, Session Controller, Client UI packages, and Web bundle remain Team-agnostic. Source-checkout users must add two ordered experimental profile layers to a Web profile. Promotion renames the experimental npm packages but does not require a new generated namespace.
中文
问题
持久 Agent Teams runtime 负责 roster、mailbox 与 task 状态，但只提供模型工具和 Host service method。Web 用户需要查看 teammate 活动、按同样的 compare-and-set 规则管理共享任务，并打开 teammate 会话。Agent Teams 仍处于实验阶段，因此这些能力不能向稳定 API Proxy、Session Controller、Client UI package 或 Web bundle 增加 Team 专用 contract 或依赖。
决策
私有 ctx.agentTeams service 除 domain operation 外，还直接负责生成式 agentTeams/view、agentTeams/createTask 与 agentTeams/updateTask Remote method。Team package 负责浏览器安全的 view 与 mutation-result type。View 包含 roster 与当前 task 状态，但不包含 pending mailbox 内容或已删除 task tombstone。Create 与 update rejection 通过封闭 business result 跨越 Remote；过期的 update revision 保留为 team-task-conflict，其他 Team rejection 保留为 team-rejected。意外 failure 仍是普通 RemoteResult failure。
@deepseek-ai/dsh-experimental-client-ui-agent-team 通过稳定 ctx.remote service 挂载 @deepseek-ai/dsh-experimental-agent-team/remote contribution，随后直接消费生成式 ctx.remote.agentTeams method，不增加 Client result 包装层。它展示 roster status、model 与 diagnostics，并支持 task create、edit、dependency update、assignment、completion、reopen 与 deletion。每次 update 都发送当前显示的 revision。每个 create 或 update 都独立持有 pending token，在开始前使更早的 refresh 失效，并在成功后重新读取完整 Team view。Conflict 仅在其 reload 成功后要求用户检查；如果重新读取失败，则保留该错误。重叠 refresh 只发布所选 Session 的最新请求。
Teammate navigation 使用既有 { parentSessionId, childSessionId, mode: 'continuable' } Subagent address，不带 Team tag。UI 刷新直接 child catalog、再次检查所选 Session，然后打开 addressed conversation。History 与后续人类 prompt 使用稳定 Subagent 路径；Team mailbox 只用于 Team 工具发起的 Team peer delivery。
@deepseek-ai/dsh-experimental-agent-team-web-profile 在稳定 Web bundle 之后只插入 UI。它与 Host 侧 @deepseek-ai/dsh-experimental-agent-team-profile 一起应用，后者已经插入 ctx.agentTeams 与模型工具。两个稳定 bundle 都不包含禁用的 Team row 或依赖。
稳定 Web preset 仍会在自身 preset scope 内注册 continuable Subagent control。顶层 Agent Teams profile override 无法替换这些 registration，因此该实验性 composition 可能同时暴露 Team roster 与 legacy child control。Team-aware Web preset 暂缓实现；Web profile README负责记录当前限制。
边界
Web UI 不提供 mailbox timeline、worktree 或 Git control、teammate creation、rename、deletion、interrupt 或自动 merge。它不会从 task ownership 或 write scope 推断文件系统权限。导航到 teammate 后的人类 continuation 是普通 addressed-child prompt，不是 Team mailbox message。
考虑过的替代方案
扩展 legacy API Proxy Team RPC map。 拒绝，因为这会把实验性 domain 放入稳定 wire package，并重复生成式 Remote vocabulary 与 validation。
引入独立的浏览器 Remote service。 拒绝，因为这些 method 没有区别于 ctx.agentTeams 的状态、lifecycle 或 policy owner；第二个 Cordis service 会重复 Team injection，并要求另一个 package 提供同一个 Typert namespace。
向稳定 Subagent address 与 prompt routing 添加 Team metadata。 拒绝，因为普通 child navigation 已经标识会话；Team tag 会让稳定 Client 与 Subagent contract 耦合实验性 mailbox policy。
在稳定 Web bundle 中加入禁用 Team row。 拒绝，因为禁用 row 仍会产生 release 依赖，并让实验性 package 成为随附 composition 的一部分。
测试
Team service 单元测试、生成流程与 plain-Node built-artifact smoke 校验直接 Remote method、error mapping 与导出 descriptor。Client typecheck 与浏览器 component test 覆盖挂载 namespace、Lead routing、原始生成式 result、所有 task action、独立 pending operation、完整 task board reload、成功及失败的 conflict reload、陈旧 async result、navigation、dispose 与状态或错误呈现。Web 端到端测试先断言 overlay 等于两个随附实验性 profile 层，再运行真实 Host Remote flow。
后果
Team service 是 domain state 与公开选定 Team value 的 Remote operation 的唯一 Cordis owner。稳定 API Proxy、Session Controller、Client UI package 和 Web bundle 保持 Team 无关。源码 checkout 用户必须向 Web profile 添加两个有序 experimental profile 层。Promotion 会重命名实验性 npm package，但不要求新的生成式 namespace。