Página Principal Explorar Ajuda
Registe-se Iniciar Sessão
haiany
/
deepseek-harness
mirror de https://github.com/deepseek-ai/deepseek-harness.git
1
0
Fork 0
Ficheiros Problemas 0 Wiki
Ramo: master
Ramos Etiquetas
deepseek-harnes...
/
packages
/
experimental
/
client-ui-agent-team
/
README.md

README.md 5.1 KB
Link permanente Histórico Em bruto

description: "Use and debug the experimental Web Agent Teams roster, shared task board, and teammate navigation panel."

kind: "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 Web profile. The browser projection does not extend the stable API Proxy, store Team state, or register model-facing input.

Table of Contents

Use this package

Install the package through @deepseek-ai/dsh-experimental-agent-team-web-profile after the stable Web bundle and the Host-side Agent Teams profile. 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, runtime status, model, and diagnostics. Selecting a healthy teammate refreshes the existing direct-child catalog and opens the ordinary { parentSessionId, childSessionId, mode: 'continuable' } address. 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

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`](../agent-team/README.md), 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`](src/client/mount.ts) | Generated Remote, locale, navigation, and slot registrations | | [`src/client/TeamAction.tsx`](src/client/TeamAction.tsx) | Roster and task-board interaction state | | [`src/client/locales.ts`](src/client/locales.ts) | English and Chinese panel copy | | [`src/index.ts`](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.