@toddzheng024/dscode-desktop 0.7.34 → 0.7.36

package/README.md

@@ -3,7 +3,7 @@
 DSCODE adds a coding preset, browser workflows, cross-session collaboration,
 memory and task management to the official DeepSeek Harness Desktop application.
 
-**Version:** 0.7.34 · **Harness runtime:** 0.2.0-rc.2
+**Version:** 0.7.36 · **Harness runtime:** 0.2.0-rc.2
 
 Preview release candidate; publication is a separate step.
 
@@ -37,8 +37,9 @@ desktop_dsh='/Applications/DeepSeek Harness.app/Contents/Resources/runtime/cli/b
 "$desktop_dsh" plugin --profile desktop add /absolute/path/to/dscode-desktop.tgz --ignore-scripts
 ```
 
-Restart Desktop, select the **DSCODE** preset, select a workspace, and configure
-the model under **Settings → DSCODE models** or **DSCODE accounts**.
+Fully quit and reopen Desktop. In **Settings → General**, enable **Show coding view**; enable **Agent presets** in Plugins if disabled. Create a new session and select **DSCODE** and a workspace. Use an existing model from the normal model picker.
+
+**Settings → DSCODE** contains setup, Models, Accounts and Schedules at the same level. Models and Accounts add optional providers; they are not required for existing Desktop accounts. **Plugins → DSCODE · Community** opens the same page. The package activation notice explains the required restart.
 
 Installation through the official **Plugins → Add plugin** interface was checked
 on macOS Desktop 0.2.0-rc.2. Public npm installation instructions accompany a
@@ -47,7 +48,7 @@ public release; a candidate build alone does not publish a package.
 ## Install a published version
 
 After this version is available on npm, enter
-`@toddzheng024/dscode-desktop@0.7.34` in **Plugins → Add plugin**,
+`@toddzheng024/dscode-desktop@0.7.36` in **Plugins → Add plugin**,
 review the installation, install, then choose **Enable now**. Using the exact
 version keeps the installation tied to these instructions and compatibility
 requirements. The `preview` tag tracks the current Desktop preview release.
@@ -81,9 +82,9 @@ configuration and the user patch. Keep a backup before migrating your own state.
 - Durable session messaging, source-backed memory and opt-in scheduling.
 - Email inbox, IMAP/Gmail setup and explicit message-to-session delivery.
 - Independent code review, optional automatic permission review and diagnostics.
-- Plugin Hub search, categories and details, read-only conversation discovery,
-  and reviewed installation through the official plugin manager. Enable and
-  configure installed plugins in **Settings → Plugins**; see `docs/plugin-hub.md`.
+
+Plugin Hub is not bundled: this package does not add its settings page, catalog
+connection or discovery tools. See `docs/plugin-hub.md` for version boundaries.
 
 Use the bundled guides under `docs/` for individual settings and boundaries.
 The terminal's state directory may differ from Desktop's; sharing credentials

package/cordis.patch.yml

@@ -42,14 +42,14 @@
 - insert:
     - id: dscode-credentials
       name: "@toddzheng024/dscode-desktop/credentials"
+      config:
+        desktop: true
     - id: dscode-desktop-workspace
       name: "@toddzheng024/dscode-desktop/workspace"
     - id: dscode-custom
       name: "@toddzheng024/dscode-desktop/custom"
     - id: dscode-desktop
       name: "@toddzheng024/dscode-desktop"
-    - id: dscode-hub
-      name: "@toddzheng024/dscode-desktop/hub"
     - id: dscode-openrouter
       name: "@toddzheng024/dscode-desktop/openrouter"
       config:
@@ -92,8 +92,6 @@
           cursorVisualization: visible
     - id: dscode-desktop-triggers
       name: "@toddzheng024/dscode-desktop/triggers"
-    - id: dscode-browser
-      name: "@toddzheng024/dscode-desktop/browser"
     - id: dscode-auto-review
       name: "@toddzheng024/dscode-desktop/auto-review"
 
@@ -431,3 +429,6 @@
 
           - id: present
             name: '@deepseek-ai/dsh-tool-present'
+
+          - id: dscode-browser
+            name: '@toddzheng024/dscode-desktop/browser'

package/docs/CHANGELOG.md

@@ -6,7 +6,25 @@ Per-release notes live in [`docs/releases/`](releases/); the entries below summa
 
 <!-- Add upcoming changes under Unreleased. -->
 
-## [Unreleased]
+## [0.7.36] - 2026-10-09
+
+### Added
+
+- `dscode acp` serves standard ACP stdio clients with the DSCODE agent preset and configured providers. It supports native DSH session controls and forwards approval requests to the client. See [ACP clients](acp.md) for setup and inherited protocol limitations.
+
+- The source and npm launchers preserve ACP stdin/stdout, use client tool approvals, and require an installed-protocol probe before Hub publication.
+- Linux CI pulls the official Node image through its ECR Public mirror to avoid Docker Hub anonymous pull limits.
+
+## [0.7.35] - 2026-10-08
+
+- Promote the verified Desktop package to both `preview` and `latest` so default installations receive this fix instead of 0.7.33. Promotion requires a matching public-install receipt.
+
+- Scope Desktop browser tools, skill and command to DSCODE sessions. Standard sessions no longer inherit the DSCODE browser entry; TUI Browser Use keeps its existing integration.
+- Group setup, Models, Accounts and Schedules under one DSCODE settings page, using Harness theme tokens and compact controls. Add a community-labeled Plugins item and an activation notice with full-restart and preset-selection instructions.
+- Prefer existing native Desktop credentials and save new Desktop keys to the native store. Terminal credentials remain a legacy fallback; explicit removal clears both copies. Existing Desktop models do not require a separate DSCODE login.
+
+- Remove bundled Plugin Hub functionality from the Desktop package: no Hub settings page, catalog endpoint, conversation discovery tools, source files or Hub-specific runtime dependencies. DSCODE's catalog listing and release synchronization remain available; this does not publish a standalone Hub Desktop plugin. Already published 0.7.34 packages retain their previous contents; update to 0.7.35 to remove the integration.
+- Update the Desktop demo and browser guide to distinguish DSCODE's integration features from official Harness Browser Use, and replace bundled-Hub qualification with checks that the package and running Host contain no Hub integration.
 
 ## [0.7.34] - 2026-10-08
 

package/docs/acp.md

@@ -0,0 +1,31 @@
+# ACP clients
+
+Run `dscode acp` to expose the DSCODE agent preset through Agent Client Protocol over newline-delimited JSON-RPC on stdin/stdout. The terminal interface is disabled. The ACP client supplies an absolute workspace directory when creating a session; tools run on the computer running DSCODE.
+
+## Connect a client
+
+Configure your client's custom ACP agent with executable `dscode` and arguments `["acp"]`. If the editor cannot find commands installed through nvm, use the absolute path printed by `command -v dscode`. Keep stdin open for the lifetime of the connection.
+
+To select an initial model explicitly, use:
+
+```sh
+dscode acp --model custom-your-provider-id/your-model-id
+```
+
+Without `--model`, the bridge uses DSCODE's saved default provider and model. Set up credentials and custom services in the normal TUI first with `/login` or `/provider custom`. The stable custom provider ID is recorded in `~/.dscode/providers.yaml`; it is not the service's display name. API keys stay in the existing credential store. Clients supporting ACP configuration options can select an advertised model and reasoning effort after creating a session.
+
+For a source checkout, the equivalent executable is `node` with arguments `["/absolute/path/to/dscode/bin/dscode.mjs", "acp"]`. Source and npm installations use their existing, separate state directories. `--patch FILE` adds a trusted composition overlay and can be repeated. `dscode acp --help` prints usage without starting the runtime or installing a profile.
+
+## Behavior and limits
+
+- New and resumed ACP agents mount the `dscode` preset, including its tools and provider adapters. The bridge reuses DSH's native ACP implementation rather than translating terminal output.
+- ACP sessions use the `ask` permission preset. Tool requests requiring approval are sent to the ACP client; the client can allow once, reject, or cancel. Normal sandbox rules still apply. The terminal's automatic model review is not the approval decision maker for these sessions.
+- Standard session creation, prompts, cancellation, model configuration, listing, resume, close and MCP attachment are inherited from the pinned DSH bridge. Resume reconnects a session without replaying its transcript.
+- The inherited bridge identifies itself as `deepseek-harness-acp`. It does not advertise `session/load`, modes, slash commands, terminal delegation, client filesystem operations or interactive question forms. Clients requiring those features need additional integration; a successful protocol handshake does not establish full editor compatibility.
+- Title generation, session-card generation and memory generation are disabled in this transport. Configured providers, tools and other integrations remain available; ACP is not an offline mode.
+- Stdout is reserved for protocol frames. First-install progress and launcher diagnostics go to stderr. Trusted custom patches must also respect this rule.
+- Closing stdin shuts down the runtime. SIGTERM is forwarded by the launcher. Sessions persist in the same installation's state directory, and a running ACP process holds the normal installation lock against upgrades.
+
+## Verification
+
+`node scripts/verify-acp.mjs` exercises the source CLI with a fixture model and custom API, without paid model requests. Unit tests cover argument validation, preset composition, source and npm launcher routing, cleanup and signal forwarding. Client-specific UI behavior must be verified in the intended editor.

package/docs/browser-use.md

@@ -5,6 +5,27 @@ DevTools MCP. Chrome starts only when you use `/browser start` or the agent call
 `browser_start`. No MCP configuration or separate npm installation is needed.
 Google Chrome is required for browser tasks; ordinary coding does not need it.
 
+## Relationship to official Harness Browser Use
+
+Official Harness already provides a [Browser Use framework and experimental
+providers](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/browser-use/README.md),
+including Chrome DevTools MCP, Playwright MCP and Stagehand. Basic page browsing,
+clicking, typing, screenshots and developer inspection are not unique DSCODE
+features. Backend and Session lifecycle plumbing overlap with upstream work.
+
+DSCODE adds its own per-origin access and separate Developer grants, screenshot
+point annotations delivered to the conversation, and explicit login handoff and
+resume controls. The sections below describe their behavior and limits. These
+are DSCODE integration features; this guide does not claim that every upstream
+provider lacks equivalent capabilities.
+
+The official [Browser sidebar](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/client/ui-sidebar-browser/README.md)
+embeds a web view and does not itself register model tools. DSCODE's Browser
+preview captures an external Chrome connection. It does not drive that embedded
+web view, share its login state automatically, or present a live browser stream.
+Persistent profiles, Chrome attachment and experimental extension/WebMCP support
+are additional DSCODE connection choices, not evidence of better task quality.
+
 ## Start a task
 
 From this checkout, run `npm start`, then ask:
@@ -625,7 +646,7 @@ and account settings, browser preview, durable session communication, cross-sess
 memory and opt-in task scheduling together. Ordinary builds remain private;
 the separate [release process](hub-distribution.md#desktop-release-candidate-and-publication)
 qualifies a public candidate for 0.2.0-rc.2. The Desktop preview is published on npm as
-`@toddzheng024/dscode-desktop@0.7.34`. The package does
+`@toddzheng024/dscode-desktop@0.7.35`. The package does
 not yet include all DSCODE Host services. Its experimental
 [native Computer Use adapter](computer-use.md) has passed helper and lifecycle
 checks; window observation, screenshots and input await qualification with
@@ -633,9 +654,9 @@ macOS Accessibility permission.
 Choose this package or the browser-only bundle; enabling both duplicates their
 browser services.
 
-The Desktop plugin's package name is `@toddzheng024/dscode-desktop`. It also
-includes [Plugin Hub](plugin-hub.md) for community discovery and installation
-through the official manager. The earlier private
+The Desktop plugin's package name is `@toddzheng024/dscode-desktop`. Version 0.7.35
+removes bundled [Plugin Hub](plugin-hub.md) functionality; older 0.7.33 and 0.7.34
+packages still include it. The earlier private
 `@toddzheng024/dscode-desktop-preset-probe` must be removed before installing
 this package; both register the same DSCODE components. Back up your Desktop
 state first. A separate macOS Desktop 0.2.0-rc.2 migration check preserved
@@ -717,20 +738,15 @@ desktop_package='/absolute/path/printed-by-pack-command.tgz'
 "$desktop_dsh" plugin --profile desktop add "$desktop_package" --ignore-scripts
 ```
 
-Reopen Desktop, choose **DSCODE** for a new session, and configure a model under
-**Settings → DSCODE models**, or connect a supported account under
-**Settings → DSCODE accounts**. Browser preview is available in the right sidebar.
-**Settings → DSCODE schedules** manages tasks for an open DSCODE session and
-explicitly enables or stops delivery. Its launch preference is saved; Desktop
-must remain open to deliver tasks. See [Desktop scheduling](triggers.md#experimental-desktop-scheduling)
-for restart, removal and permission behavior, and current qualification limits.
-
-The account page saves or removes the shared OpenRouter API key. Changes also
-affect terminal sessions and native routes reading that same credential file;
-environment-owned keys remain read-only. The saved key is never returned to the
-form. Choose **DSCODE OpenRouter** in the model picker for DSCODE reasoning
-controls, including Ultra on supported models. The native OpenRouter route
-remains available separately.
+Fully quit and reopen Desktop after installing or updating. In **Settings → General**, enable **Show coding view** and enable **Agent presets** in Plugins if disabled. Create a new session with **DSCODE**; existing sessions keep their original preset. Choose a model from the normal picker to reuse an existing Desktop account.
+
+In 0.7.35 and later, **Settings → DSCODE** groups Get started, Models, Accounts and Schedules as peer entries and follows the host's light/dark theme. **Plugins → DSCODE · Community** opens the same setup page. Models and Accounts are optional additions. Published 0.7.34 still has separate settings pages.
+
+Browser tools, the browser skill and `/browser` are mounted only in DSCODE sessions. Standard sessions retain their existing tools, and the DSCODE preview explains the preset boundary instead of starting a browser there. TUI Browser Use remains enabled through its existing composition. The Desktop package still supplies shared credential and subagent compatibility services; this scope change does not remove those Host adapters.
+
+**Settings → DSCODE → Schedules** manages tasks for an open DSCODE session and explicitly enables or stops delivery. Its launch preference is saved; Desktop must remain open to deliver tasks. See [Desktop scheduling](triggers.md#experimental-desktop-scheduling) for restart, removal and permission behavior, and current qualification limits.
+
+Desktop credentials now prefer the existing native store and save new keys there. Existing terminal keys remain a fallback when no native key is present; saving a Desktop key does not replace the terminal key. Explicit key removal clears both copies to prevent a legacy key from becoming active again. Environment-owned keys remain read-only, and the saved key is never returned to the form. Choose **DSCODE OpenRouter** for DSCODE reasoning controls, including Ultra on supported models. The native OpenRouter route remains available separately.
 
 For Grok, run `grok login` in a terminal and refresh the account status. DSCODE
 reads `~/.grok/auth.json` without changing or refreshing its tokens. For OpenCode

package/docs/custom-providers.md

@@ -36,7 +36,7 @@ editor and discovering models again does not replace it with a server-reported
 output limit. Models whose output budget has never been edited can still adopt
 the server's reported value.
 
-In Desktop's **Settings → DSCODE models**, **Discover models** immediately merges the returned models into the draft. Existing models keep their order, thinking mode and image-input choice; new models are appended. Reported limits refresh unless you have edited that value, including an output budget you deliberately left blank. Models absent from the response remain in the draft. Choose **Save provider** to persist the changes.
+In Desktop's **Settings → DSCODE → Models**, **Discover models** immediately merges the returned models into the draft. Existing models keep their order, thinking mode and image-input choice; new models are appended. Reported limits refresh unless you have edited that value, including an output budget you deliberately left blank. Models absent from the response remain in the draft. Choose **Save provider** to persist the changes.
 
 Thinking defaults to the server's behavior. Identified oMLX models also offer Off/On in the editor and Off/On in `/effort` (the stored effort IDs are `off` and `high`). Other custom APIs do not receive guessed reasoning parameters. Native Responses reasoning items and Anthropic thinking signatures are retained for replay to the same service, model and protocol.
 
@@ -44,7 +44,7 @@ Thinking defaults to the server's behavior. Identified oMLX models also offer Of
 
 In the model editor, set **Input → Text and images** only when that model and endpoint support image input. Existing configurations and newly discovered models default to **Text only**; DSCODE does not infer vision support from a model name. Discovery preserves your explicit choice. Changing the base URL, API format or model ID resets the editor's image choice to **Text only**, so enable it again for the new deployment.
 
-In the [experimental Desktop package](browser-use.md#install-the-experimental-combined-desktop-package), open **Settings → DSCODE models**, select the saved provider, enable the model's **Accepts images** checkbox and choose **Save provider**. Select that saved model in the session's model picker. The same explicit capability setting and request-image limits apply in both interfaces. The settings test checks text, streaming and tools; it does not test image understanding.
+In the [experimental Desktop package](browser-use.md#install-the-experimental-combined-desktop-package), open **Settings → DSCODE → Models**, select the saved provider, enable the model's **Accepts images** checkbox and choose **Save provider**. Select that saved model in the session's model picker. The same explicit capability setting and request-image limits apply in both interfaces. The settings test checks text, streaming and tools; it does not test image understanding.
 
 All three protocols can send user images, browser annotation screenshots and images returned by tools. DSCODE reads their durable attachments and sends image bytes to the configured API: Chat Completions uses `image_url` data URLs, Responses uses `input_image`, and Anthropic Messages uses base64 `image` blocks. Tool screenshots follow their tool result as user image content. Enabling this option does not add vision capability to a text-only server.
 
@@ -64,7 +64,7 @@ Automatic review follows its configured model route. When that route is Custom,
 
 ## Persistence
 
-Service and model configuration lives in `~/.dscode/providers.yaml`; keys use the existing owner-only `~/.dscode/credentials.yaml` store. Provider records contain no key values. Each service receives a stable `custom-…` ID and a derived `DSCODE_CUSTOM_CUSTOM_…_API_KEY` credential reference. An environment variable with that exact reference takes precedence over the saved key, following the existing credential-store rules.
+Service and model configuration lives in `~/.dscode/providers.yaml`; terminal keys use the existing owner-only `~/.dscode/credentials.yaml` store. In Desktop 0.7.35 and later, existing native credentials take precedence and new keys are saved to the native Harness store (`~/.dsh/.credentials.yaml` by default). Old DSCODE keys remain a fallback; explicit removal clears both copies to avoid reactivating a legacy key. Provider records contain no key values. Each service receives a stable `custom-…` ID and a derived `DSCODE_CUSTOM_CUSTOM_…_API_KEY` credential reference. An environment variable with that exact reference takes precedence over the saved key, following the existing credential-store rules.
 
 Configuration is shared across projects and installed versions, written atomically, and reloaded by other running Hosts. Stale editors cannot overwrite newer configuration. Renaming a service preserves its ID, so persisted sessions continue to resolve it. Removing a provider removes its route and writable stored credential; it does not reroute existing sessions or delete their history. An environment-supplied key remains in the environment. If it masks a stored key, clear the environment override before removing the provider to remove that stored key too.
 

package/docs/demo.md

@@ -2,84 +2,68 @@
 
 ## Desktop feature summary
 
-The 0.7.34 Desktop preview installs into official Harness Desktop. Its qualified
-target is macOS Apple Silicon with Harness runtime **0.2.0-rc.2**. Present the
-DSCODE workflow and the Plugin Hub contribution separately:
+The 0.7.35 Desktop preview installs into official Harness Desktop.
+Its qualified target is macOS Apple Silicon with runtime **0.2.0-rc.2**.
+This version removes bundled Hub functionality. Demonstrate DSCODE on its own
+and state which version is being shown.
 
 | Area | What the user gains | Boundary |
 | --- | --- | --- |
 | DSCODE coding workflow | A DSCODE preset with custom model/account settings, session communication, memory, usage and delegation views | Terminal-only panels retain their terminal UI; model behavior depends on the configured provider. |
-| DSCODE browser workflow | Browser tools, per-site access, a screenshot preview and point annotations in the conversation | Chrome is required. An image-capable model is needed to interpret screenshots; captures expire and must be refreshed after navigation. |
+| DSCODE browser integration | Per-site and Developer permissions, screenshot preview and point annotations delivered to the conversation, manual login handoff | Official Harness already has Browser Use. DSCODE connects external Chrome; it does not enhance or share login state with the official embedded browser. |
 | DSCODE optional services | Email inbox integration and scheduled work | Account configuration and explicit opt-in are required. Desktop must stay open for scheduled delivery. |
-| Our Plugin Hub integration | Search and categories across our community catalog, package details, compatibility and reported scan information, plus read-only discovery tools for the agent | Catalog coverage defines the search scope. Reported scans do not establish that a plugin is safe. |
-| Hub installation handoff | Review an exact npm version, confirm its installation and open official management | Official Harness inspects and installs it. New plugins remain disabled; official controls own enabling, configuration and removal. |
 
-The Hub story is **find → understand → review → install → manage**. Its value is
-community discovery and the information needed to choose a plugin. Do not count
-DSCODE's browser, memory or coding features as Hub features, or claim that Hub
-replaces official lifecycle management. This demo makes no claim that every
-official Desktop version lacks search.
+Hub community discovery belongs in a separate product demo. The removal does
+not deliver a standalone Hub Desktop package. See [Plugin Hub](plugin-hub.md)
+for the behavior of earlier published versions.
 
 ## Five-minute Desktop walkthrough draft
 
-This draft is for existing DSH Desktop users. Choose the final emphasis and
-recording length with the presenter; allow separate time for downloads and
-account setup. The installation and UI paths have verification records, but
-this complete timed walkthrough has not been rehearsed with a live model.
+Allow separate time for downloads and account setup. This complete timed
+walkthrough has not been rehearsed with a live model.
 
 ### Prepare
 
-1. Use a disposable Desktop profile and a scratch workspace. Install
-   `@toddzheng024/dscode-desktop@0.7.34` through **Plugins → Add plugin**, then
-   choose **Enable now**. Select the **DSCODE** preset. Follow the
-   [installation guide](browser-use.md#install-the-experimental-combined-desktop-package)
-   if migrating from the old probe package.
-2. Configure a model in private, confirm one short response and install Chrome.
-   For the annotation segment, choose a model whose configuration accepts images.
-   Do not record API keys, account login or personal workspace contents.
-3. Open **Settings → Plugin Hub**, search for `dsh-theme-plugin`, and check the
-   current details and compatibility. The recorded installation check used
-   **0.3.3**; the live catalog may offer a newer exact version. Rehearse that
-   version before using it in a recording. An incompatible or unavailable entry
-   is a reason to show discovery only, without claiming installation succeeded.
-4. Keep the [0.7.34 release page](https://github.com/qiz029/dscode/releases/tag/v0.7.34)
-   ready for the installation and distribution closing shot. The public npm
-   package and GitHub archive carry the same qualified bytes.
+1. Use a disposable Desktop profile and scratch workspace. For the published
+   demo, install `@toddzheng024/dscode-desktop@0.7.35` through **Plugins → Add
+   plugin**, then choose **Enable now**. Fully quit and reopen Desktop after
+   updating. Hub is separate from this package. For local development builds,
+   follow the [installation guide](browser-use.md#install-the-experimental-combined-desktop-package)
+   and identify the checkout being demonstrated.
+2. Select the **DSCODE** preset when creating the session. Harness 0.2.0-rc.2
+   gates the preset picker behind **Show coding view**; ensure that option and
+   the Agent presets UI are enabled before recording. A Standard session does
+   not acquire the complete DSCODE preset just because the package is installed.
+3. Configure a model in private, confirm one short response and install Chrome.
+   For annotations, choose a model that accepts images. Do not record API keys,
+   account login or personal workspace contents.
+4. Rehearse one small coding task and the browser annotation with that model.
+   Keep the matching release page or local-build information ready. A local
+   build must not be presented as the published 0.7.35 archive.
 
 ### Walkthrough
 
 | Approximate time | Action | Point to explain |
 | --- | --- | --- |
-| 0:00–0:30 | Show the enabled DSCODE plugin and a DSCODE session in official Desktop. | Existing DSH Desktop users can add DSCODE through a plugin. |
-| 0:30–1:30 | Open Plugin Hub, search, choose a category and open details. | Our Hub brings community discovery, descriptions and compatibility information into the application. |
-| 1:30–2:30 | Choose **Review installation**, show the exact package/version, then **Confirm installation**. Wait for its actual outcome. | The user reviews the package; official Harness performs installation. Download time is additional. |
-| 2:30–3:00 | Choose **Manage installed plugin**, show its disabled state and official controls. | Enabling, configuration and removal stay in official management. Enabling the example theme is optional. |
-| 3:00–4:30 | In the DSCODE session, ask: “Use the browser to open https://example.com and inspect the page.” Grant that origin if requested. In **Browser preview**, refresh the image, select a point, type “Summarize the text at this point” and choose **Send annotation**. | This is DSCODE's browser workflow. The screenshot, page reference and selected point enter the conversation; show the real response only after it arrives. |
-| 4:30–5:00 | Show the exact npm install specification and GitHub release assets/notes. | Users can install the released plugin today; releases include compatibility, changes and verification limits. |
-
-For a Hub-only cut, keep the first four rows and the release closing shot. No
-model account is needed to browse and install through the Hub UI. For a longer
-DSCODE cut, add a scratch-project coding task and demonstrate the relevant
-usage/delegation view after rehearsing it with the selected model.
+| 0:00–0:30 | Show the enabled DSCODE plugin and a DSCODE session. | Existing DSH Desktop users can add the coding workflow through a plugin. |
+| 0:30–2:00 | Run the rehearsed small coding task in the scratch workspace. | Show actual changes and verification; model quality is not established by the installation checks. |
+| 2:00–4:00 | Ask the agent to open https://example.com. Grant that origin if requested. In **Browser preview**, refresh, select a point, enter “Summarize the text at this point” and choose **Send annotation**. | Basic browsing overlaps official Browser Use. The demonstrated DSCODE additions are the permission controls and screenshot/point handoff into the conversation. |
+| 4:00–4:30 | Open the session usage view; show the delegation view only if the task actually delegated. | Views reflect the current DSCODE session and available records. |
+| 4:30–5:00 | Show the matching install specification and release notes, or label the local build. | Published availability and an unreleased change are distinct states. |
 
 ### Rehearsal and reset
 
-- Confirm the selected package is absent before the install shot. Remove a
-  previous demo installation through official **Plugins** in the disposable
-  profile, then reopen Hub. Do not remove plugins from a personal profile to
-  prepare the demonstration.
-- Show success, cancellation, refusal or restart-required exactly as reported.
-  After a Host restart, inspect official **Plugins** before attempting another
-  installation; Hub operation history does not survive the restart.
-- If the Hub/network is unavailable, use a clearly identified earlier recording
-  or continue with the DSCODE segment. Do not label cached footage as a live
-  successful install.
-- Refresh the browser screenshot and select a new point if the capture expires
-  or navigation occurs. Text-only delivery must be described as text-only.
-- Keep standalone DMG delivery, coordinated update/changelog UI, Profile
-  rollback and native Computer Use permission qualification out of this demo's
-  claims. See [Plugin Hub](plugin-hub.md), [Browser use](browser-use.md) and the
-  [release notes](releases/0.7.34.md) for the shipped behavior and limits.
+- Reopen Desktop after a package update. Confirm both plugin activation and a
+  working new DSCODE session before starting the recording.
+- Refresh the screenshot and select a new point after navigation or expiry.
+  Image understanding needs an image-capable model. Describe text-only delivery
+  as text-only.
+- Stop the session browser between rehearsals. Its Chrome profile and login
+  state are separate from the official embedded browser.
+- Keep standalone DMG delivery, Hub integration, coordinated update/changelog
+  UI, Profile rollback and native Computer Use permission qualification out of
+  this demo's claims. See [Browser use](browser-use.md) and the
+  [0.7.35 release notes](releases/0.7.35.md) for published behavior and limits.
 
 ## The 90-second terminal demo
 

package/docs/hub-distribution.md

@@ -37,15 +37,16 @@ A user who already has dsh-hub installed can apply directly, but must use pnpm 1
 
 Install the official Harness Desktop application with embedded runtime
 0.2.0-rc.2. In **Plugins → Add plugin**, enter
-`@toddzheng024/dscode-desktop@0.7.34`, review and install, then choose
-**Enable now**. Select the DSCODE preset and configure your model account.
+`@toddzheng024/dscode-desktop@0.7.35`, review and install, then choose
+**Enable now**. Fully quit and reopen Desktop, enable **Show coding view** and
+**Agent presets**, then create a DSCODE session and choose an existing model.
 The Desktop preview is qualified on macOS Apple Silicon. See
 [Desktop installation](browser-use.md#install-the-experimental-combined-desktop-package)
 for archive checksums, migration and removal, and [Plugin Hub](plugin-hub.md)
-for discovering community plugins after installation.
+for the separation between DSCODE and Hub.
 
 Version 0.7.34 fixes the 0.7.33 activation error “4 entries did not activate”
-when Desktop starts without `DSH_HOME`. Update to the exact 0.7.34 package and
+when Desktop starts without `DSH_HOME`. Update to the current 0.7.35 package and
 enable it again; exporting a shell variable is unnecessary. Default Desktop
 state uses `~/.dsh`, as resolved by Harness. Publication now verifies installation
 and the affected components with that default environment.
@@ -135,8 +136,8 @@ node scripts/verify-desktop-registry.mjs .research/desktop-release-runtime --loc
 `prepare:desktop` provisions exact direct dependencies with install scripts
 disabled; it refuses to overwrite an unrelated project. `release:desktop`
 builds a public candidate only for Harness 0.2.0-rc.2, then unpacks those exact
-bytes for Host startup/restart, browser, annotation, isolation and authenticated
-Hub RPC checks. The source runtime is checked for unintended changes. The
+bytes for Host startup/restart, browser, annotation and isolation checks, plus
+checks that Hub files, UI, tools and endpoint are absent. The source runtime is checked for unintended changes. The
 local install rehearsal additionally resolves dependencies in a new native
 Harness profile and boots the installed package; it does not establish public
 npm availability or drive the Electron UI.
@@ -154,6 +155,7 @@ npm run publish:desktop -- credentials
 npm run publish:desktop -- npm
 npm run publish:desktop -- hub
 npm run publish:desktop -- verify
+npm run publish:desktop -- promote
 ```
 
 Each phase checks the archive and receipt again. The npm phase publishes with
@@ -166,8 +168,11 @@ version retry up to 40 times, 15 seconds apart. Other rejections and credential
 errors stop immediately; the final integrity and compatibility checks still
 apply. The final phase downloads public bytes,
 checks their SHA-256, and installs the exact npm version into a new native
-Harness profile before booting it and checking the preset and Hub RPC. The
-result is saved as `artifacts/local/desktop-public-install.json`. No model
+Harness profile before booting it and checking the preset and absence of bundled Hub tools and endpoint. The
+result is saved as `artifacts/local/desktop-public-install.json`. The `promote`
+phase requires this public receipt to match the candidate, then updates npm
+`latest` to the same version as `preview`. Both entry points serve the current
+qualified preview; the Desktop support boundary remains unchanged. No model
 account is used, and no real-model quality claim follows from these probes.
 
 The existing npm token must permit the new Desktop package. Successful `whoami`
@@ -175,7 +180,7 @@ proves authentication only; the first publish establishes write permission.
 Desktop publication does not replace the terminal profile, create a DMG, or
 implement an automatic Desktop updater. GitHub Release attaches the Desktop
 archive, checksum and instructions alongside the terminal assets. Follow the
-[Plugin Hub guide](plugin-hub.md) for discovery and official management.
+[Plugin Hub guide](plugin-hub.md) for the separation from DSCODE and earlier-version behavior.
 
 ### Login-free publishing (local machine)
 

package/docs/plugin-hub.md

@@ -1,68 +1,35 @@
-# Plugin Hub in Harness Desktop
+# DSCODE and Plugin Hub
 
-The DSCODE Desktop plugin includes **Settings → Plugin Hub**, backed by
-[DSH Plugin Hub](https://dshpluginhub.ai). It uses the same public catalog as
-the Hub website and CLI. No Hub login is required to browse.
+DSCODE and [DSH Plugin Hub](https://dshpluginhub.ai) are separate products.
+Installing DSCODE should not also install a Hub browsing interface.
 
-## Find and inspect plugins
+## Version 0.7.35 and later
 
-Enter a package name or describe a capability, optionally choose a category,
-and select **Search**. **Load more plugins** continues the current search.
-Open **View details** to read the description, repository, license, weekly
-downloads, publisher indicators, reported security checks and declared
-compatibility. The website link opens the corresponding Hub listing.
+The Desktop build no longer includes the Hub settings page, Host endpoint,
+`plugin_hub_search` or `plugin_hub_info` tools, Hub source files or Hub-specific
+runtime dependencies. DSCODE sessions do not require the community catalog to
+start or use coding and browser features.
 
-Publisher verification and a passing scan do not guarantee safety. Missing,
-failed and incomplete scans remain visible. Compatibility declarations come
-from the catalog; the official installer also checks the actual package.
+The package retains its catalog listing metadata so people can discover DSCODE
+through Hub. Release-time catalog synchronization and the terminal launcher's
+existing Hub distribution mechanism remain in place. Neither adds the Desktop
+Hub interface to a user's DSCODE installation.
 
-In a DSCODE conversation, ask the agent to find a plugin. The read-only
-`plugin_hub_search` and `plugin_hub_info` tools use the same catalog and Desktop
-compatibility checks. These tools do not install plugins, change the Profile
-or expose account credentials. Catalog descriptions are third-party data.
-The native Standard preset does not receive these tools.
+Hub discovery is available on the separate website. This change does not publish
+a standalone Hub Desktop plugin or move Hub into the official Plugins page.
 
-## Install and enable
+## Published versions 0.7.33 and 0.7.34
 
-1. Open the package details and choose **Review installation**.
-2. Review the exact npm package, version and registry returned by the official
-   plugin manager, alongside the Hub's scan and compatibility information.
-3. Choose **Confirm installation**. The official manager downloads the package
-   and dependencies. **Cancel installation** requests cancellation through that
-   manager; the displayed outcome determines whether it completed in time.
-4. Select **Manage installed plugin**, then enable and configure it in the
-   official **Settings → Plugins** page.
+These releases still contain **Settings → Plugin Hub**, catalog search and
+categories, package details, and the two read-only discovery tools in DSCODE
+sessions. Their installation handoff delegates to the official plugin manager;
+enabling, configuration and removal stay in **Settings → Plugins**.
 
-Installation leaves the plugin disabled. Enabling third-party plugins runs
-their code in the Host. Build-script approvals, enable/disable, configuration
-and removal remain with the official plugin manager. When it reports a failure,
-cancellation, override or restart requirement, the Hub preserves that outcome.
-It does not report every completed package command as successful activation.
+Installing or reinstalling 0.7.34 will therefore not remove the bundled Hub.
+Update to `@toddzheng024/dscode-desktop@0.7.35` using the [Desktop installation guide](browser-use.md#install-the-experimental-combined-desktop-package).
+Fully quit and reopen Desktop after updating; an already running Host may keep
+the old plugin modules loaded.
 
-An installation preview expires after five minutes. Reopen the preview if it
-expires. Closing and reopening the Hub page recovers the latest operation while
-the same Host remains running. After a Host restart, check **Plugins** before
-retrying; the Hub's operation history is not persisted.
-
-## Current boundaries
-
-- The first integration installs the catalog's latest exact npm version. It
-  checks DSH and Node ranges, platform, interface support, withdrawal and
-  deprecation. Git/tarball-only entries remain discoverable but are not installed
-  through this integration.
-- Already available bundles link to official management. This page does not
-  replace them, select older versions, check for updates or roll back a Profile.
-- Searches cover the community catalog, including packages for other Harness
-  interfaces. Details explain when a package does not fit this Desktop.
-- The DSCODE terminal package and Desktop package are separate entries. A
-  terminal-only package is not made Desktop-compatible by appearing in search.
-- Search queries and package lookups go to `api.dshpluginhub.ai`. Provider keys,
-  conversation text, workspace files and local credentials are not sent by this
-  catalog client. The agent may include task terms in a query you ask it to make.
-- The Desktop plugin is published as `@toddzheng024/dscode-desktop@0.7.34`
-  on npm, with the `preview` tag. Official Add plugin installation, Hub installation with
-  handoff to official management, and migration from the legacy probe name
-  have passed on macOS Desktop 0.2.0-rc.2.
-
-See [Desktop installation](browser-use.md#install-the-experimental-combined-desktop-package)
-and [distribution](hub-distribution.md) for package setup and release status.
+Historical Hub installation and UI verification applies to those earlier
+versions. It does not establish availability of a separate Hub Desktop package.
+See [distribution](hub-distribution.md) for release gates.

package/docs/releases/0.7.35.md

@@ -0,0 +1,31 @@
+# DSCODE 0.7.35
+
+This release separates DSCODE from Hub, confines its Desktop browser integration to DSCODE sessions, and aligns setup and settings with Harness Desktop.
+
+- **Desktop browser boundaries:** browser tools, the browser skill and `/browser` are mounted in DSCODE sessions. Standard sessions retain their own tools; DSCODE preview refuses to start a browser from another preset. TUI Browser Use keeps its existing lazy Chrome integration. Shared Desktop credential and subagent compatibility services remain installed.
+- **Hub separation:** the Desktop package no longer contains Hub UI, discovery tools, endpoint, source files or Hub-specific dependencies. DSCODE remains discoverable through the Hub catalog, and the terminal's Hub distribution continues. This release does not provide a separate Hub Desktop plugin. Older 0.7.33/0.7.34 packages retain their published contents.
+- **Setup and interface:** Settings → DSCODE groups Get started, Models, Accounts and Schedules as peer entries, using Harness theme tokens and compact controls. Plugins → DSCODE · Community opens the same page. Activation guidance explains a full application restart, Show coding view, Agent presets and creating a DSCODE session. Existing sessions keep their preset; host-owned list icons remain unchanged.
+- **Existing accounts:** use the normal model picker for models already configured in Desktop. Native credentials take precedence and new Desktop keys are saved to the native store. Legacy terminal keys remain a fallback; explicit removal clears both copies to prevent reactivation and warns before confirmation. External account sign-in flows keep their existing behavior.
+- **Default distribution:** after an exact public installation passes, both npm `preview` and `latest` point to this Desktop version. This replaces the stale default 0.7.33 entry while retaining the preview support boundary. Publication requires the public-install receipt to match the archive.
+
+Update in official **Plugins → Add plugin** with `@toddzheng024/dscode-desktop@0.7.35`, then fully quit and reopen the application. Enable **Show coding view** in General and **Agent presets** in Plugins if needed; create a new session and select **DSCODE**. A window close alone does not restart the Host.
+
+Verification before release: `npm run check` passed 1,079 unit/component cases,
+both TypeScript checks, coverage, integration/package checks and 63 eval cases.
+Real Chrome checks passed for the TUI and independent Harness 0.2.0-rc.2
+Desktop Host, including screenshot/annotation transport, permissions,
+Standard/DSCODE isolation and repeated session creation before/after restart.
+The signed macOS application passed installation, upgrade from public 0.7.34,
+incompatible-update rejection, removal/reinstallation and data preservation.
+Light/dark setup, models, accounts, schedule empty state and the Plugins entry
+were inspected in the official shared client attached to an isolated Desktop
+Host. The final release workflow requalifies the exact versioned archives.
+
+The first local full run included a scheduler cleanup timeout; its isolated
+suite and the full rerun passed without scheduler code changes. The user's
+intermittent inactive-context failure was not reproduced, and hot reload is
+not qualified. Full restart remains required. Live-model task quality,
+external account login, individual mail/usage/delegation panel visual rehearsal,
+macOS Computer Use Accessibility qualification and other platforms/runtimes
+remain unverified by this release. The Desktop target is macOS Apple Silicon,
+Harness runtime 0.2.0-rc.2; no standalone DMG is included.