Team Workspace for DeepSeek Harness

The current DSH conversation is Leader. This Cordis plugin registers the same six compact Team Workspace tools, forwards their calls to dist/server.cjs, and supplies identity from exec.agent.id and the exact live ctx.sessions entry. It does not start a second coordinator.

Install the published npm package through the DSH plugin manager, with dependencies tools, sessions, agents, and sessionProjections available. For DSH 0.1.7-rc.2, the profile's native delegation tool normally defaults to subagent; its exact tool schema comes from the active native request header. Team execution requires a profile with native subagent delegation and the send_message / interrupt_agent controls. Use the host's configured provider and model defaults.

The ./client browser export registers 团队工作区 in the native conversation header. Clicking it opens a native tab in the host’s right Sidebar, with the conversation making room beside it. The host owns resize, collapse, tab close, and narrow-screen fullscreen. Repeated opens reuse the page in the active pane. Task details expand inside the panel; owner buttons navigate to member sessions. Its own teamWorkspace projection reads the authenticated current Leader's engine team, stable task IDs, and verified member session bindings. The public SDK folds complete team-workspace/state non-surface events; they do not enter model history. Live root agents are polled serially every two seconds, unchanged states renew at most once per ten seconds, and failed reads never renew evidence. A view older than twenty seconds disables navigation. Without an engine team, the separately labeled official native agentTeam view remains available. Clicking a task owner opens the uniquely verified current member session; missing or ambiguous owners cannot navigate. Every click rechecks the native session binding, current team, freshness, and mainView retention. This panel performs navigation only; it does not send messages or start turns.

On DSH's durable spawn_teammate profile, provider selects a registered spawn transport (the installed spawn-in-process), not an arbitrary model provider. Native send_message can steer or resume an inactive teammate and can wake the Lead; an accepted/queued delivery is not execution completion. The in-process spawn provider does not inherit the parent's tool/authority restrictions. Native permission presets govern sandbox and approval behavior separately; advisory write scopes are not a native filesystem sandbox. No extra transport, model route, authority inheritance, or cross-Claude/OpenCode execution is implied.

Native installation

In the DSH plugin manager, enter [email protected] after this version is published to npm. For an existing CLI profile:

dsh plugin --profile <existing-profile> add [email protected]
dsh --profile <existing-profile> --dump-config

DSH reads dsh.bundle.patch, adds the bundle to the profile, and resolves the plugin by its npm package name. No absolute path editing or install-time build is needed. This package includes its compiled native entry and MCP server and does not install the DSH runtime or a second model client. Desktop profiles are managed by the Desktop application; use its plugin manager rather than the CLI.

Optional developer staging

A ZIP is a developer staging artifact, not the native npm install route. The repository's scripts/install-host.mjs helper rewrites the bundle entry to the staged dist/index.mjs absolute path. Activate the resulting developer overlay:

dsh --profile <existing-profile> --patch <staged-package>/cordis.patch.yml

To verify composition without starting a model, add --dump-config. For manual staging, first replace name: 'agent-team-deepseek-harness' with the absolute entry path; profile-relative resolution cannot locate an unrelated staged folder.

dist/index.mjs has no DSH runtime package imports. MCP and Node dependencies are bundled. TEAM_WORKSPACE_SERVER_PATH can override the bundled server; TEAM_WORKSPACE_NODE_BINARY selects the Node executable. bridgeRoot is an optional plugin configuration field; the same path is passed to the MCP child.

Public progress uses session/event, coalesced for 100 ms; terminal events and tool calls flush immediately. Only native turn/end establishes a terminal turn. An interrupt receipt remains a request. A session mounted after its historical events have occurred reports unknown history until live events arrive.

The view is mounted through the native conversation header slot. Native tool results also provide the team state. No project URL, Codex session, or automatic chat message is used.

Protocol tests do not invoke paid models. Native model delegation and full interactive workflow require validation in the user's configured DSH profile.