Files
deepseek-harness/packages/experimental/client-ui-agent-team

description, kind
description kind
Use and debug the experimental Web Agent Teams roster, shared task board, and teammate navigation panel. package-reference

@deepseek-ai/dsh-experimental-client-ui-agent-team

English | 中文

Summary

This package adds an Agent Teams action to the Web conversation header, where a user can inspect the current roster, manage the shared task board, and navigate into a teammate's conversation. It reads authoritative Team state through the generated ctx.remote.agentTeams contribution and keeps ordinary child-history navigation on the stable addressed-subagent path. Choose it through the published experimental Agent Teams bundle. The browser projection does not extend the stable API Proxy, store Team state, or register model-facing input.

Table of Contents


Use this package

Enable this package through @deepseek-ai/dsh-experimental-agent-team-profile, which supplies the Team service, tools, and Web UI together. The Web Client loader mounts the /client export; the root Host export is inert, and the package has no user configuration fields.

Inspect and navigate the roster

Opening the panel calls agentTeams/view. Roster rows show durable names, turn availability, model, and diagnostics. Provisioning and running members use the shared ongoing loader, inactive members use idle, and failed members use error. Selecting a healthy teammate opens the ordinary { parentSessionId, childSessionId, mode: 'continuable' } address from its Lead and roster identity without refreshing or checking the parent catalog. The Host validates the parent, child, and mode when history opens. History and later human prompts continue through the stable addressed-subagent conversation path; this package adds no Team-specific address field.

Manage the task board

Ready pending tasks use idle, blocked pending tasks use warning, in-progress tasks use ongoing, and completed tasks use done.

The task board shows task identity, owner, blockers, readiness, advisory write scopes, and overlap warnings. A user can create, edit, assign or unassign, complete, reopen, and delete tasks through agentTeams/createTask and agentTeams/updateTask. Every update sends the displayed revision, and create or update rejections remain explicit business results.


Understand the implementation

Implementation internals — click to expand

The Client export mounts the generated ctx.remote.agentTeams contribution from @deepseek-ai/dsh-experimental-agent-team/remote, then registers its locale dictionaries and one conversation-header slot through Cordis effects. Disposing the plugin fiber removes both registrations.

Starting a create or update invalidates older refreshes. Success reloads the complete Team view so every task's derived fields stay current. A team-task-conflict result displays a stale-state notice only after that reload succeeds; a reload failure remains visible instead. Editing task text or scopes and changing dependencies use two sequential compare-and-set mutations because the Team service exposes them as separate actions.

File Role
src/client/mount.ts Generated Remote, locale, navigation, and slot registrations
src/client/TeamAction.tsx Roster and task-board interaction state
src/client/locales.ts English and Chinese panel copy
src/index.ts Inert Host entry

Further Exploration


Model Experience

None, as this browser projection and task control surface registers no model-facing input.

KV Cache effect

No direct effect; the Team tools and ordinary conversation submission own any later model-visible use.

Known Limitations and Deferred Work

  • Snapshot refresh — the panel refreshes on open, explicit refresh, and mutations; it has no live event subscription or mailbox timeline.
  • Ordinary child continuation — a human message sent after navigation uses the stable addressed-subagent prompt path, not the Team peer mailbox.
  • No lifecycle or workspace controls — the panel cannot spawn, rename, delete, or interrupt teammates, and write scopes remain advisory metadata.

Dev Note

Working context for maintainers — click to expand

None.

Runtime invariant: No companion is published. RPC is authoritative and the package owns only one disposable slot registration.