@jingyi0605/codingns4dsh 0.2.1-beta.5 → 0.2.1-beta.6

package/README.en.md

@@ -1,8 +1,8 @@
 <div align="center">
 
-# Codingns4DSH
+# CodingNS for DeepSeek Harness
 
-**External Agent CLIs, persistent terminals, workspace debug and remote access — inside DSH's own UI.**
+**Use multiple coding Agents, manage projects, talk with your assistant, and access your DSH workbench remotely.**
 
 [![npm version](https://img.shields.io/npm/v/%40jingyi0605%2Fcodingns4dsh?logo=npm)](https://www.npmjs.com/package/@jingyi0605/codingns4dsh)
 [![DSH compatibility](https://img.shields.io/badge/DSH-0.2.1--alpha.1-4D6BFE)](https://github.com/deepseek-ai/deepseek-harness)
@@ -11,7 +11,7 @@
 
 [简体中文](README.md) · **English**
 
-**Current release `@jingyi0605/codingns4dsh@0.2.1-beta.5`** · DSH **`>=0.2.0-rc.2 <=0.2.1-alpha.1`** (tested with `0.2.1-alpha.1`) · Node **`>= 22.19`** · macOS / Linux / Windows
+**Current release `@jingyi0605/codingns4dsh@0.2.1-beta.6`** · DSH **`>=0.2.0-rc.2 <=0.2.1-alpha.1`** (tested with `0.2.1-alpha.1`) · Node **`>= 22.19`** · macOS / Linux / Windows
 
 **[GitHub](https://github.com/jingyi0605/Codingns4DSH)** · **[npm](https://www.npmjs.com/package/@jingyi0605/codingns4dsh)** · **QQ group 1092985965** · **[WeChat / QQ QR codes](#community)**
 
@@ -19,7 +19,7 @@
   <a href="#interface-preview">Preview</a> ·
   <a href="#what-is-codingns4dsh">What it is</a> ·
   <a href="#supported-agents">Agents</a> ·
-  <a href="#feature-details">Features</a> ·
+  <a href="#features">Features</a> ·
   <a href="#installation">Install</a> ·
   <a href="#first-run">First run</a> ·
   <a href="#troubleshooting">Troubleshooting</a> ·
@@ -43,71 +43,62 @@ The CodingNS workbench brings the conversation, Agent picker and Git sidebar tog
 
 ## What is Codingns4DSH
 
-**DSH (DeepSeek Harness)** is a coding-agent harness — a CLI plus Web UI that runs an agent loop inside your workspace.
+**Codingns4DSH** is a plugin for [DSH (DeepSeek Harness)](https://github.com/deepseek-ai/deepseek-harness) that brings coding Agents, project tools and a personal assistant into one workbench. Manage all modules in **Settings → Codingns4DSH**.
 
-**Codingns4DSH is a DSH plugin bundle** (Host + browser layers) adding eleven modules, all configured under **Settings → Codingns4DSH**.
-
-> Naming: this plugin is **Codingns4DSH** (npm package `@jingyi0605/codingns4dsh`; its settings entry is labelled Codingns4DSH). **Codingns4DSH** on its own refers to the platform service that provides the Control API, accounts and the relay tunnel.
-
-| Module | What it does | Default |
+| Module | What you can do | Default |
 | --- | --- | :---: |
-| **External Agent integration** | Run installed Agent CLIs as native DSH sessions: streaming, tools, approvals, questions, usage, thinking levels | On |
-| **Workspace session enhancement** | Agent logos on session rows, archived-session entry, subscription/usage readout | Off |
-| **Mobile access enhancements** | On phones or narrow viewports, collapse the main sidebar, turn the settings navigation into an icon rail, support horizontal swipes, Android vibration and LAN PWA notifications | On |
-| **Terminal enhancement** | Persistent terminals plus shell, theme, font, cursor and scrollback settings | Off · restart |
-| **LAN access to DSH** | Listener forwarding a LAN address to the local DSH Web port, with a status indicator and one-click copy of a usable access URL | Always on |
-| **Login protection** | One optional local account guarding LAN **and** relay access; loopback always allowed | Always on (card) |
-| **Relay access service** | **Your DSH Web from anywhere on the internet**, end-to-end encrypted | Off |
-| **Workspace debug** | Per-workspace launch profiles, port checks, HTTP service proxy | On |
-| **Git repository management** | View changes, stage files, commit and browse Git history in the right sidebar | On |
-| **File management enhancement** | Create, rename, move, copy and delete files/directories, with code and script detection | Off |
-| **PeerHost workbench** | Proxy other handshaken DSH Hosts and aggregate workspaces, sessions and scoped tools | Off |
-
-Nothing native is replaced — conversations, sessions, sidebar, settings and approvals stay DSH's own.
-
-Everything runs on the **Host** (your machine): Agents, terminals, files, LAN/relay listeners; the browser is only a view. Agent CLIs run as DSH child processes with their own credentials and providers — model traffic never goes through Codingns4DSH. Remote access is available through optional modules.
-
-Notes: the sidebar terminal exists as soon as the plugin is installed — **Terminal enhancement** only switches it to the persistent backend (tmux on macOS/Linux, ConPTY on Windows) and applies on restart; the 调试 card is currently Chinese-only.
+| **External Agent integration** | Use coding Agents in DSH, switch models and follow their work | On |
+| **Workspace session enhancement** | Identify Agents, manage archived sessions and view subscription usage | Off |
+| **Mobile access enhancements** | Use a mobile layout, sidebar gestures, home-screen access and notifications | On |
+| **Terminal enhancement** | Use persistent terminals and customize their appearance | Off |
+| **LAN access to DSH** | Open your workbench from other devices on the same network | Always available |
+| **Login protection** | Require a login for LAN and relay access | Off |
+| **Relay access service** | Access DSH over the internet with end-to-end encryption | Off |
+| **Workspace debug** | Save launch profiles, manage processes, check ports and access services | On |
+| **Git repository management** | Review changes, stage, commit, switch branches and browse history | On |
+| **File management enhancement** | Create, edit, rename, move, copy and delete files | Off |
+| **PeerHost workbench** | Use other DSH Hosts' workspaces and sessions in your current workbench | Off |
+| **Global assistant (experimental)** | Chat by text or voice, follow project progress and customize your assistant | Off |
+
+Agents, terminals and project files run on the computer hosting DSH (the Host). The browser provides a shared interface, with remote access available when needed.
 
 ---
 
 ## Supported Agents
 
-Detected on the Host by command name; version and models come from the CLI itself. Detected Agents are enabled by default and can be toggled individually. The built-in **DeepSeek Harness** Agent is always available.
-
-| Agent | id | Command | Protocol | Capabilities | Notes |
-| --- | --- | --- | --- | --- | --- |
-| Command Code | `command-code` | `command-code`, `commandcode`, `cmdc` | CLI + ACP | models, streaming, resume, interrupt, tools, thinking, usage, approvals, questions | The formal Host runtime uses `cmd acp`; DSH permissions map to `--plan`, `--permission-mode accept-edits`, or `--yolo`, and questions return through Command Code's `session/request_permission` extension |
-| Claude Code | `claude-code` | `claude` | stream-json | models, streaming, resume, interrupt, tools, thinking, usage, approvals, questions | `can_use_tool` approvals and `AskUserQuestion` |
-| Kimi CLI | `kimi` | `kimi`, `kimi-cli` | stream-json | all of the above + approvals, questions, steering | — |
-| Gemini CLI | `gemini` | `gemini` | ACP | models, streaming, resume, interrupt, tools, thinking, usage, approvals, questions | ACP permissions and form elicitation |
-| Pi Agent | `pi` | `pi`, `pi-agent` | JSON-RPC | models, streaming, resume, interrupt, tools, thinking, usage, steering | No verifiable DSH approval/question response wire in the current protocol |
-| Codex | `codex` | `codex` | JSON-RPC (app-server) | all + approvals, questions, steering | app-server enables `request_user_input`; DSH renders the native question panel |
-| OpenCode | `opencode` | `opencode`, or `OPENCODE_SERVER_URL` (default `http://127.0.0.1:4096`) | HTTP + SSE | all + approvals, questions | — |
-| Grok Build | `grok` | `grok`, `grok-build` | ACP | models, streaming, tools, thinking, usage, approvals, questions | ACP permissions plus Grok's private `x.ai/ask_user_question` structured question method |
-| MiniMax Code | `mcode` | `mcode` | ACP / stream-json | models, streaming, resume, interrupt, tools, thinking, usage, approvals, questions | Interactive requests use ACP; the explicit-effort `exec` path has no interactive response wire |
-| ZCode | `zcode` | `zcode`, bundled desktop runtime | JSON-RPC bare envelope | models, streaming, resume, interrupt, usage | No verifiable DSH approval/question response wire |
-| CodeBuddy (auto-detects CN/international) | `codebuddy` | `codebuddy`, `codebuddy-code`, `cbc`, and Windows `.cmd` entry points; region selected from environment and auth domain | ACP (`--acp`) | models, streaming, resume, interrupt, tools, thinking, usage, approvals, questions | Supports stdio ACP and HTTP sidecar ACP |
-| WorkBuddy | `workbuddy` | `codebuddy` bundled in the WorkBuddy desktop app | ACP (`--acp`) | models, streaming, resume, interrupt, tools, thinking, approvals, questions | Permissions and form elicitation use the HTTP ACP sidecar |
-| Cursor CLI | `cursor-cli` | `cursor-agent`, `agent` | ACP (`acp`) | models, streaming, resume, interrupt, tools, thinking, approvals, questions | Standard ACP permissions and form elicitation |
-| Kiro CLI | `kiro-cli` | `kiro-cli` | ACP (`acp --agent-engine v3 --auth-method cli`) | models, streaming, resume, interrupt, tools, thinking, approvals, questions | Standard ACP permissions and form elicitation |
-| Qoder | `qoder` | `qoder`, `qodercli` | ACP (`--acp`) | models, streaming, resume, interrupt, tools, thinking, approvals, questions | Standard ACP permissions and form elicitation |
-| Qoder CN | `qoder-cn` | `qodercn`, `qoderclicn` | ACP (`--acp`) | models, streaming, resume, interrupt, tools, thinking, approvals, questions | Standard ACP permissions and form elicitation |
-| Antigravity | `antigravity` | `agy` | stream-json (stdin NDJSON) | models, streaming, resume, interrupt, tools, thinking | Permission state maps to CLI safety modes; no interactive approval/question wire |
-
-**models** model list · **streaming** live output · **resume** continue after restart · **interrupt** cancel a turn · **tools** tool calls in the conversation · **thinking** reasoning/effort · **usage** token or subscription limits · **approvals / questions** native DSH interactions · **steering** inject a message mid-turn.
-
-Unlisted capabilities are unsupported by that CLI or version. Install and log in to each Agent outside DSH; Codingns4DSH never stores Agent credentials.
-
-Approvals and questions are rendered by DSH's native components. The Web Client Bundle must inject `@deepseek-ai/dsh-client-ui-user-questions`; otherwise the Host may receive a question event without having a question panel to mount. Adapters with an interactive response wire normalize Provider requests into `permission-request` or `question-request` events, pass them to the native approval/question components, then send the typed answer back with the Provider's original request ID. ACP adapters use the standard `session/request_permission` and `elicitation/create` form requests; Grok Build's `grok_build/ask_user_question` tool call returns through the private `x.ai/ask_user_question` method with an `outcome`; Command Code's `ask_user_question` also uses `session/request_permission`, distinguished by `toolCall.kind=other` and `toolCall.rawInput.question/options`. Fixed choices are returned using the original `optionId`; free text is carried in ACP `_meta["codingns/questionAnswer"]` and returned to the Command Code tool through a Node loader that only affects the child process memory and does not modify the user's installed package. The Codex app-server explicitly enables `default_mode_request_user_input` so it emits `item/tool/requestUserInput` requests. URL elicitation requires a browser security-consent flow and is not advertised. Antigravity only maps DSH permission state to CLI safety modes.
+Install and sign in to an Agent with its own tools, and Codingns4DSH will detect it. The built-in **DeepSeek Harness** Agent remains available. Choose models and view streaming replies in one interface, with session resume, tool calls and thinking controls where supported.
+
+The table highlights selected capabilities; availability depends on the Agent and its version. Skills are reusable workflows, and steering lets you add a message while an Agent is working.
+
+| Agent | Key capabilities | Notes |
+| --- | --- | --- |
+| **Command Code** | Skills, approvals, questions, usage | Uses DSH permission settings and the native question panel |
+| **Claude Code** | Skills, approvals, questions, usage | Supports native skill discovery and invocation |
+| **Kimi CLI** | Approvals, questions, steering, usage | — |
+| **Gemini CLI** | Approvals, questions, usage | Supports native approvals and form questions |
+| **Pi Agent** | Steering, thinking controls, usage | DSH approval and question responses remain unverified in the current protocol |
+| **Codex** | Approvals, questions, steering, usage | Questions appear in DSH's native question panel |
+| **OpenCode** | Skills, approvals, questions, usage | Supports a local CLI or existing server, plus native skills |
+| **Grok Build** | Skills, approvals, questions, usage | Supports native skill discovery and structured questions |
+| **MiniMax Code** | Approvals, questions, usage | Default integration supports interaction; explicit-effort execution does not return interactive responses.<br>Upstream contributor: [chenjunyi000](https://github.com/chenjunyi000)<br>PRs [#6](https://github.com/jingyi0605/Codingns4DSH/pull/6), [#7](https://github.com/jingyi0605/Codingns4DSH/pull/7) |
+| **ZCode** | Model selection, session resume, usage | Uses the CLI or the desktop app's bundled runtime.<br>Upstream contributor: [chenjunyi000](https://github.com/chenjunyi000)<br>PRs [#6](https://github.com/jingyi0605/Codingns4DSH/pull/6), [#7](https://github.com/jingyi0605/Codingns4DSH/pull/7) |
+| **CodeBuddy** | Approvals, questions, usage | Automatically detects CN/international editions.<br>CodexHost contributor: [mouzhi](https://github.com/mouzhi)<br>Initial integration: [f30b000](https://github.com/BytePioneer-AI/codex-host/commit/f30b000f88950c40844b071eec2f6f385c6bcb49) |
+| **WorkBuddy** | Approvals, questions, thinking controls | Uses the WorkBuddy desktop app's bundled runtime.<br>CodexHost contributor: [BytePioneer-AI (ChongWen)](https://github.com/BytePioneer-AI)<br>Initial integration: [6e9f365](https://github.com/BytePioneer-AI/codex-host/commit/6e9f365e2bf8ac61716f8250475530ae790f2d2f) |
+| **Cursor CLI** | Approvals, questions, thinking controls | CodexHost contributor: [mouzhi](https://github.com/mouzhi)<br>Initial integration: [ad6ba8e](https://github.com/BytePioneer-AI/codex-host/commit/ad6ba8e04d294c473d2dcad99880496ff39c1f7e) |
+| **Kiro CLI** | Approvals, questions, thinking controls | CodexHost contributor: [gy212](https://github.com/gy212)<br>Initial integration: [79675cd](https://github.com/BytePioneer-AI/codex-host/commit/79675cdbfdc042eb37a849c3eb1539e9efc40a0d) |
+| **Qoder** | Approvals, questions, thinking controls | CodexHost contributors: [gy212](https://github.com/gy212), [BytePioneer-AI (ChongWen)](https://github.com/BytePioneer-AI)<br>PR #289 merge: [8926130](https://github.com/BytePioneer-AI/codex-host/commit/8926130af1426a467747b66d8d2dbf68f7764a7b) |
+| **Qoder CN** | Approvals, questions, thinking controls | CodexHost contributors: [gy212](https://github.com/gy212), [BytePioneer-AI (ChongWen)](https://github.com/BytePioneer-AI)<br>PR #289 merge: [8926130](https://github.com/BytePioneer-AI/codex-host/commit/8926130af1426a467747b66d8d2dbf68f7764a7b) |
+| **Antigravity** | Session resume, tool calls, thinking controls | Permission settings select safety modes; no interactive approvals or questions.<br>CodexHost contributor: [gy212](https://github.com/gy212)<br>Initial integration: [ed4e785](https://github.com/BytePioneer-AI/codex-host/commit/ed4e785116642eafc08e4186e92e83f3816c7765) |
+
+Each Agent handles its own installation and login. See the [Agent adapter documentation](specs/spec007.1-外部Agent适配器扩展/README.md) (Chinese) for integration details.
 
 ---
 
-## Feature Details
+## Features
 
 ### External Agent Integration
 
-After you pick an Agent and a model, Codingns4DSH starts (or resumes) that CLI as a DSH child process and projects its event stream into a native session; the model and thinking effort are remembered per Agent.
+Choose an Agent and model to start coding. Replies, tool calls, approvals and questions appear directly in the DSH conversation. Model and thinking preferences are remembered per Agent, and you can delegate tasks to other connected Agents.
 
 <div align="center">
   <table>
@@ -118,13 +109,9 @@ After you pick an Agent and a model, Codingns4DSH starts (or resumes) that CLI a
   </table>
 </div>
 
-The model list is read from each CLI and can be switched at any time; the composer button also shows the current model and thinking effort.
-
-External Agents assemble their own requests, so the context panel's heuristic composition never matches the provider-reported usage; those sessions keep only the occupancy percentage and totals, without the System / Tools / Messages breakdown.
-
 ### Session Enhancement and Usage
 
-Session rows show the Agent logo and archive entry, and the composer dock shows subscription or upstream usage for Agents whose limits can be read (cache hit rate, per-model stats and cost included). The "Settings" button next to "Show subscription and usage" adjusts the query timeout (10 seconds by default, applied to every Agent) and the auto refresh interval (5 minutes by default, 0 disables automatic refresh); switching back to the same Agent within the interval reuses the previous result instead of querying upstream again.
+Identify sessions by Agent icons, access archived conversations, and hide or restore workspaces. Supported Agents can show subscription allowances, reset times, usage and costs.
 
 <div align="center">
   <table>
@@ -135,11 +122,27 @@ Session rows show the Agent logo and archive entry, and the composer dock shows
   </table>
 </div>
 
-Usage comes from the Agent's own quota API or a configured upstream source; it is read on the Host and never stored in the browser.
+### Global Assistant (Experimental)
+
+Create a personal assistant with your choice of name, personality, model and avatar. Open the same workbench from the sidebar or floating avatar.
+
+- **Continuous conversations**: text and live voice share one history, so you can switch input methods and keep talking.
+- **Project follow-up**: check progress in selected projects, look up sessions and send follow-up messages at your request.
+- **Web search**: use your configured DSH search service for weather, news and other current information.
+- **Attachments**: ask about images and text files; image understanding requires a vision-capable model.
+- **Avatars and voices**: use built-in or third-party avatars, customize portraits and voices, and keep calls in a floating view with captions and mute controls.
+
+Browser speech playback is the default, with local MOSS speech available as an option. The assistant handles conversation and coordination; it does not execute commands or edit code directly.
+
+### Terminals and Log Sharing
+
+The sidebar terminal is available after installation. Enable **Terminal enhancement** and restart DSH for persistent terminals. Terminals are shared within a workspace and retain their state when switching sessions.
+
+Attach terminal output or selected logs to a new or existing conversation to ask an Agent for help.
 
 ### Workspace Debug
 
-Each workspace keeps its own launch profiles (`<workspace>/.codingns/debug.json`): command, working directory, environment, shell and an optional port — start, check the port, kill the process or stop it. An optional reverse proxy exposes the port through DSH (HTTP only for now).
+Save launch profiles for each project, start or stop processes, check port status and access project HTTP services through DSH. The debug panel currently has a Chinese-only interface.
 
 <div align="center">
   <table>
@@ -150,23 +153,25 @@ Each workspace keeps its own launch profiles (`<workspace>/.codingns/debug.json`
   </table>
 </div>
 
-The panel shows live port state and PID, and issues an unguessable proxy URL per running instance.
-
 ### Git Repository Management
 
-The Git panel is opened from DSH's native right sidebar and persists per workspace across sessions. It can initialize a repository, show staged and unstaged files, stage or unstage paths, discard changes, create commits, switch branches and browse commit history. Disabling the module removes its sidebar tab and Host Git RPC without affecting other modules.
+Initialize repositories, review changes, stage or unstage files, commit, switch branches and browse history from the right sidebar.
 
 ### File Management Enhancement
 
-File management enhancement adds common file operations to DSH's native file sidebar: create files and directories, rename, move, copy and delete entries, with code and script type detection for the editor entry point. Workspace path validation rejects paths outside the active workspace; disabling the module removes its sidebar entry and Host RPC.
+Create, edit, rename, move, copy or delete files and directories directly in the file sidebar.
 
 ### PeerHost Workbench
 
-PeerHost proxies other DSH Hosts without replacing the current logged-in Host. It can add LAN peers, persist target configuration and login state, and route workspaces, sessions, chat input, live events, files, Git, terminals and right-sidebar tools through an explicit HostScope. A failing peer does not block the local Host or other peers. Unsupported native navigation surfaces report `degraded` or `unsupported` instead of creating an iframe or pretending to be a native three-column view.
+Add other DSH Hosts on your LAN to access their workspaces, sessions, files, Git and terminals from the current workbench. Hosts remain independent, so a disconnected peer does not interrupt local work. PeerHost aggregation through the relay service is not currently supported.
+
+### Mobile Access
+
+Read conversations, send messages and use workspace tools on your phone. Swipe to open or close sidebars, add the app to your home screen, and use notifications in supported browsers.
 
 ### Modules and Settings
 
-The settings page renders one card per module — switch, description and restart notice all come from the module itself; terminal appearance, LAN mapping, login protection and relay account are configured inside their own cards.
+Enable the features you need and configure them in their module cards. Settings that require a restart are clearly marked.
 
 <div align="center">
   <table>
@@ -179,26 +184,20 @@ The settings page renders one card per module — switch, description and restar
 
 ### Login Protection
 
-Off by default; once enabled on its card, one local account guards LAN **and** relay access (default session timeout 30 minutes). Authentication happens at the Host's forwarding boundary, so unauthenticated traffic never reaches DSH Web; `127.0.0.1` and `::1` are always allowed to prevent lockout.
+Set a shared local account for LAN and relay access to protect your remote workbench. Local access remains available.
 
 <div align="center">
   <img width="70%" src="assets/screenshots/login-protection.jpg" alt="Local account login page">
 </div>
 
-The password is `scrypt`-hashed in a `0600` file, and the browser only holds an `HttpOnly`, `SameSite=Strict` session cookie.
-
 ### Remote Access
 
-| | LAN access | Relay access |
+| Method | Best for | How to connect |
 | --- | --- | --- |
-| Connect from | Same local network | **Any device, anywhere on the internet** |
-| Needs | Shared network + open listen port | Host can reach the Control API over HTTPS; your device can reach the Codingns4DSH entry |
-| Local port exposed | Yes — chosen interface/port (default `13080`) | No — isolated device tunnel |
-| Account | Optional login protection | Codingns4DSH account + bound Host |
+| **LAN access** | Computers, phones or tablets on the same network | Enable the mapping and copy the access URL |
+| **Relay access** | Reaching your workbench while away | Sign in to the relay service and bind your Host |
 
-**LAN**: pick a listen interface and port, auto-detect (or type) the local DSH Web port, start, then open `http://<lan-ip>:<port>` from another device; auto-start restores the mapping, and the module patches the `crypto.randomUUID` that plain-HTTP origins need.
-
-**Relay**: set the Control API (default `https://channel.codingns.com:1443`, where you can register), log in, refresh devices, bind the current Host (label, public key, fingerprint), then open the bound Host from any device through **`https://dsh.codingns.com`** — no public IP, port forwarding or VPN.
+The relay needs no public IP, port forwarding or VPN. Register at the [Codingns4DSH relay platform](https://channel.codingns.com:1443), then connect to a bound Host from the [remote workbench](https://dsh.codingns.com). Connections are end-to-end encrypted, so the relay cannot read conversation content.
 
 <div align="center">
   <table>
@@ -209,102 +208,58 @@ The password is `scrypt`-hashed in a `0600` file, and the browser only holds an
   </table>
 </div>
 
-The account entry next to DSH's Settings button shows login state, access path and latency, host CPU/memory, and offers one-click logout.
-
 <div align="center">
   <img width="70%" src="assets/screenshots/relay-status.jpg" alt="Account status popover: access path, latency, CPU and memory">
 </div>
 
-The “access” line tells you whether you entered DSH Web locally, over the LAN or through the relay.
-
-**Why the relay cannot read your DSH traffic** — the tunnel is end-to-end encrypted, so using it never hands your conversations to a server:
-
-- Payload travels in a **WebRTC DataChannel protected by DTLS between the DSH Client and the DSH Host**; direct or via TURN, only ciphertext crosses the relay.
-- The relay and control service handle **control-plane metadata only**: account/device records, Host binding, tickets, SDP/ICE signaling, online state, traffic accounting.
-- Each Host keeps its own DTLS certificate (`~/.config/codingns4dsh/dtls-identity.json`) and publishes a SHA-256 fingerprint the remote side verifies during the handshake — a mismatch aborts the connection (`Host DTLS fingerprint 校验失败`) instead of accepting a substituted certificate; the same fingerprint shows in the relay card for manual comparison.
-- Passwords are used only for login requests; refresh token and device credential stay on the Host. Diagnostics log protocol metadata only (direction, type, stream id, status, bytes) — never bodies, tickets, cookies or DSH Web content.
+The account menu shows login status, access method, connection latency and Host load.
 
 ---
 
 ## Installation
 
-**Requirements**: DSH `>=0.2.0-rc.2 <=0.2.1-alpha.1` (tested with `0.2.1-alpha.1`) · Node.js `>= 22.19` · `pnpm` on `PATH` (`dsh plugin` forwards to pnpm) · optional: Agent CLIs, and `tmux` on macOS/Linux for persistent terminals (`brew install tmux` / `sudo apt install tmux`).
-
-### Simplest install: use the built-in `web` profile
+**Requirements**: DSH `>=0.2.0-rc.2 <=0.2.1-alpha.1` (tested with `0.2.1-alpha.1`), Node.js `>=22.19`, and pnpm. Persistent terminals on macOS/Linux also require tmux.
 
-DSH automatically initializes the `web` profile on first use. You do not need to create a config file or run `--dump-config`:
+### Use the Built-in Web Profile
 
 ```bash
-dsh plugin --profile web add @jingyi0605/codingns4dsh@0.2.1-beta.5
+dsh plugin --profile web add @jingyi0605/codingns4dsh@0.2.1-beta.6
 dsh web
 ```
 
-### Optional: use a separate profile
+### Optional: Use a Separate Profile
 
-If you do not want to modify the built-in `web` profile, create a separate profile. Here `--dump-config` only initializes and inspects the profile; it is not required for installing the plugin:
+Create a separate environment from the built-in Web profile:
 
 ```bash
 dsh codingns --from-default-profile web --dump-config
-dsh plugin --profile codingns add @jingyi0605/codingns4dsh@0.2.1-beta.5
+dsh plugin --profile codingns add @jingyi0605/codingns4dsh@0.2.1-beta.6
 dsh codingns
 ```
 
-- **Do not** use `dsh plugin --profile <new-name> add ...` to create a separate profile that needs the Web UI: it initializes from `@deepseek-ai/dsh-base` only, then fails with `entry "terminal-controller" not found`. Use `--from-default-profile web` for a separate profile.
-- A registry 404 means that version is not published yet — use the source install below.
-
-```bash
-# optional: verify the installation
-dsh plugin --profile web list --depth 0           # -> codingns4dsh <version>
-
-# upgrade, pin, uninstall (restart DSH afterwards)
-dsh plugin --profile web add @jingyi0605/codingns4dsh@<version>
-dsh plugin --profile web remove @jingyi0605/codingns4dsh
-```
-
-**From source** (npm unavailable, or running a checkout):
-
-```bash
-git clone https://github.com/jingyi0605/Codingns4DSH.git && cd Codingns4DSH
-pnpm install && pnpm build
-dsh plugin --profile web add "$PWD"                # or: npm pack, then add ./jingyi0605-codingns4dsh-0.2.1-beta.5.tgz
-dsh web
-```
-
-A directory install links the checkout — rebuild (`pnpm build` / `pnpm dev:watch`) and restart DSH after changes.
-
-**State on disk**: settings live in `$DSH_HOME/settings.yaml` (default `~/.dsh/settings.yaml`) under the `codingns:` namespace.
-
-| Path | Contents |
-| --- | --- |
-| `$DSH_HOME/profiles/<profile>` | Installed plugin packages and `dsh.profile.bundles` |
-| `$DSH_HOME/codingns4dsh/` | Terminal `host-id` and `terminals.json` (restore mapping) |
-| `~/.config/codingns4dsh/` | Relay credentials, DTLS identity, login-protection hash |
-| `<workspace>/.codingns/debug.json` | Debug launch profiles (mode `0600`, secrets rejected) |
+Restart an existing DSH instance after installation or upgrade. To upgrade, replace the version in the install command with your target version. To uninstall, run `dsh plugin --profile web remove @jingyi0605/codingns4dsh`; replace `web` with your profile name when using a separate profile.
 
 ---
 
 ## First Run
 
-1. `dsh codingns` opens the DSH Web UI.
-2. Open **Settings → Codingns4DSH** to review the module cards (restart-required ones show both the effective and next-start state).
-3. Install and log in to your Agent CLIs **outside** DSH, keep them on the Host `PATH`, then enable them in **外部Agent集成**.
-4. Pick an Agent, model and thinking level in the composer and send a prompt — output streams into a native session with the Agent's logo.
-5. Right sidebar: Terminal for a workspace shell (enable **终端强化** + restart for persistence); 调试 to add a launch profile and watch its port.
-6. For remote use, turn on **登录保护**, configure **局域网访问DSH**, or log in to **中转访问服务** to connect from any network; the account entry shows the current path and host load.
+1. Open **Settings → Codingns4DSH** and enable the modules you need.
+2. Install and sign in to an Agent on the DSH Host, then choose the Agent and model in the composer.
+3. Use the right sidebar for terminals, Git, files and workspace debugging.
+4. Enable the global assistant, create your character and start chatting; prepare voice resources in voice settings for live calls.
+5. For access from other devices, configure LAN or relay access and enable login protection as needed.
 
 ---
 
 ## Troubleshooting
 
-- **Versions** — `dsh --version`, `dsh plugin --profile web list --depth 0` (replace `web` for a separate profile), `npm view @jingyi0605/codingns4dsh version`; startup rejects DSH outside the supported range, and installation does too whenever it can identify the runtime actually in use.
-- **Install-time rejection from a stale `dsh` on `PATH`** — installation only blocks on the host-injected version, the Desktop Runtime root, and a `@deepseek-ai/dsh` resolvable from the profile; `dsh --version` from `PATH` is advisory and never blocks. Runtime still validates the DSH that actually loaded.
-- **`patch: entry "terminal-controller" not found`** — the profile lacks the Web app layer; recreate it from the `web` template as shown above.
-- **Agent not detected** — run `<cli> --version` on the Host; ensure its directory is on the `PATH` of the process that started DSH (GUI launchers often differ); log in with the vendor tool, then restart DSH.
-- **Terminal** — persistent mode needs `tmux` on macOS/Linux; enabling/disabling the module and changing the binding scope need a restart; terminals are addressed per workspace.
-- **LAN** — check the card's status indicator and access URL, allow the port through the firewall, keep both devices on one network; with several DSH instances pick the detected port manually; sign in first when login protection is on.
-- **Relay** — verify Control API reachability, log in again if the session expired, refresh devices, then bind the Host.
-- **Logs** — `CODINGNS4DSH_TUNNEL_DEBUG=1 dsh codingns --no-open` (metadata only); pnpm install logs live in `$DSH_HOME/profiles/<profile>/.plugin-manager/logs/`.
-- **Reporting** — include DSH and Codingns4DSH versions, OS, module and exact error: [GitHub Issues](https://github.com/jingyi0605/Codingns4DSH/issues) or QQ **1092985965** ([WeChat / QQ QR codes](#community)).
+- **Installation fails**: check the required DSH, Node.js and plugin versions; create separate profiles from the Web template.
+- **Agent not detected**: make sure it is installed, signed in, and its command is available to the process running DSH.
+- **Terminal is not persistent**: enable Terminal enhancement and restart DSH; macOS/Linux require tmux.
+- **Voice unavailable**: check resource status in voice settings and allow browser microphone access.
+- **Remote connection fails**: check the network and firewall for LAN access, or login status and Host binding for relay access.
+
+When reporting an issue, include DSH and plugin versions, your OS and the full error: [GitHub Issues](https://github.com/jingyi0605/Codingns4DSH/issues) or the [community groups](#community).
 
 ---
 
@@ -333,40 +288,36 @@ The WeChat QR code is generated dynamically by WeChat and is **valid for 7 days*
 
 ## Development
 
-Requires Node `>= 22.19` and pnpm:
+Use a separate Stage0 environment for source development and follow the [project rules](AGENTS.md) (Chinese). Build, test and type-check commands:
 
 ```bash
 pnpm install
-pnpm build            # version check -> tsc -> client + H5 bundles
-pnpm test             # build, then the full test suite (currently 901 cases)
+pnpm build
+pnpm test
 pnpm typecheck
-pnpm run capability:check   # capability retirement check
 ```
 
-Dev loop: `pnpm dev:watch` with `pnpm dev:link <profile>`, then restart DSH. Versions come from `version.json` (`version:set-plugin` / `version:set-dsh`, guarded by `version:check`).
+Source links and development runs are for Stage0 only. Desktop uses published versions, not source links or local development packages. See the [Stage0 development notes](docs/开发记录/20261007-Stage0自动编译与热重载接入记录.md) (Chinese) for setup.
 
-Layout: `src/host` (Host layer), `src/client` (browser layer), `src/dsh-capabilities` (capability registry and version routing), `src/shared/contracts`, `src/transport` (tunnel + WebRTC), `src/features` (module registry), `tests/`, `specs/`, `docs/`, `data/build` (git-ignored).
-
-A `v*` tag runs GitHub Actions (tag/version check, frozen install, typecheck, tests, `npm pack`) and publishes with provenance; prereleases get the `next` dist-tag. Releases also run DSH installation replay, runtime module resolution and per-file npm artifact checks.
-
-Screenshot assets and shot list: [assets/screenshots](assets/screenshots/README.md) (Chinese).
-
-**Chinese version: [README.md](README.md)**
+Design and implementation details live in the [specifications](specs/), [development records](docs/开发记录/) and [development guidelines](docs/开发规范/) (Chinese). The [avatar catalog](assets/assistant-avatar-catalog.md) and [screenshot list](assets/screenshots/README.md) are also available separately.
 
 ---
 
 ## Acknowledgements
 
-The inspiration for Codingns4DSH — and part of its implementation approach — comes from **[CodexHost](https://github.com/BytePioneer-AI/codex-host)**, which runs Pi, Claude Code, Grok Build and other Harnesses natively inside Codex Desktop. It showed the direction Codingns4DSH follows from the other side: host *other* Harnesses as first-class Agents instead of replacing them. The multi-Harness adapter model, projecting a CLI event stream into native sessions, and keeping each Agent's sessions in the host sidebar and composer trace back to that design. Thanks to its authors and community.
+Thanks to **[CodexHost](https://github.com/BytePioneer-AI/codex-host)** and its community for the inspiration and implementation references for multi-Agent integration. Codingns4DSH is an independent project and is not affiliated with CodexHost.
 
-Codingns4DSH is an independent project and is not affiliated with CodexHost.
+Thanks to the adapter contributors and upstream contributors:
+
+- [chenjunyi000](https://github.com/chenjunyi000): MiniMax Code, ZCode ([#6](https://github.com/jingyi0605/Codingns4DSH/pull/6), [#7](https://github.com/jingyi0605/Codingns4DSH/pull/7)).
+- [mouzhi](https://github.com/mouzhi): CodeBuddy, Cursor CLI.
+- [BytePioneer-AI (ChongWen)](https://github.com/BytePioneer-AI): WorkBuddy, Qoder.
+- [gy212](https://github.com/gy212): Kiro CLI, Qoder, Antigravity.
 
 ---
 
 ## License
 
-Codingns4DSH is released under the **GNU General Public License version 3 or later** (SPDX: `GPL-3.0-or-later`); the full terms are in [LICENSE](LICENSE), and the `license` field in `package.json` matches.
+Released under the **GNU General Public License version 3 or later** (`GPL-3.0-or-later`). See [LICENSE](LICENSE) for the full terms.
 
 Copyright (C) 2026 jingyi0605
-
-You may use, modify and distribute the project freely under the terms of the license; derivative works must stay under the same license, ship the complete source and keep the copyright notice, and the project comes with no warranty.