dsh-open-with

Open a registered DeepSeek Harness Workspace in an installed local editor from the Web GUI. The Workspace 锟斤拷 menu launches the preferred editor directly and exposes an editor chooser when more than one launch target is available.

English | 锟斤拷锟斤拷

Demo

Hover a Workspace, open its 锟斤拷 menu, use the chevron beside the preferred editor, and choose any detected target. The recording above uses the real Harness Web UI and opens the repository in Cursor.

What it does

• The Host detects installed VS Code, Cursor, Windsurf, Zed, common JetBrains IDEs, the platform terminal, and the platform file manager where a reliable launch route exists. Operator-configured profiles can add targets or override built-ins.
• The primary row opens the Workspace in the Host default or browser-remembered editor. Its chevron opens the available-editor menu; a selection launches that editor and becomes the browser's preferred choice.
• Missing configured editors remain visible as disabled rows with a resolution hint. Missing automatic candidates stay out of the menu.
• The client uses sidebar.workspaces.row-menu when the Host declares it and otherwise installs a scoped compatibility adapter for client builds that do not yet expose that slot.
• Editor processes detach after launch and outlive the DSH Web server.

Supported launch targets

PATH lookup applies on every platform. macOS and Windows also probe the standard application locations encoded by each built-in profile. Detection runs when the Host plugin loads; restart DSH after installing an editor or changing configuration.

Prerequisites

• At least one detected built-in or configured editor executable.
• DSH 0.1.0-rc.5 or newer. A newer runtime may provide the native Workspace row-menu slot; older compatible clients use the scoped adapter.

Install

Add the plugin to the Web profile:

dsh plugin --profile web add https://github.com/ChuanTianML/dsh-open-with/archive/refs/tags/v0.1.1.tar.gz

Restart the Web server with SIGTERM, wait for it to exit, and refresh the page. Never use kill -9; it can interrupt a Session zstd write. Confirm the installed version with:

dsh plugin --profile web list dsh-open-with --depth 0

Configuration

All deployment choices are validated Cordis configuration fields:

Example:

- id: dsh-open-with
  name: dsh-open-with
  config:
    defaultEditor: cursor
    editors:
      - id: fleet
        label: Fleet
        command: fleet
        args: []

Editor ids use lowercase letters, numbers, dots, underscores, and hyphens. Duplicate custom ids, empty labels, and invalid ids fail plugin load. A custom profile whose id matches a built-in replaces that built-in launch plan, which supports variants such as VS Code Insiders without exposing commands to the browser.

Capability boundary

The browser receives only editor ids, labels, availability, and resolution hints. Commands and arguments never cross the wire. An open request carries only a Workspace id and an editor id; the Host resolves the Workspace through ctx.workspaceRegistry and the editor through its validated allowlist before spawning anything.

The plugin opens only a currently registered Workspace whose directory still exists. It never reads, writes, clones, synchronizes, or uploads Workspace files. It registers no model tool, skill, prompt, or model-visible event. The launch needs no Agent approval because it follows an explicit user click in the Workspace menu.

The preferred editor is browser-local state. Different browsers can choose different defaults without changing Host configuration.

The preference changes only after the Host accepts a launch. Failures leave the prior choice intact and appear as a transient browser alert. On compatibility clients, keyboard navigation temporarily reveals the otherwise hover-only Workspace action buttons.

Development

The repository expects a sibling DeepSeek Harness checkout at ../dsh for linked development dependencies.

pnpm install
pnpm run check

pnpm run check runs typecheck, lint, tests, and the production build. Commit lib/ because file-profile installs do not build the package.

The strict Typert descriptors in src/contract.ts are shared by the Host manifest and client Remote contribution. The Host editor registry owns executable discovery and command privacy; the Workspace registry owns id-to-path resolution. The Harness owns the row-menu slot declaration, while the plugin keeps a narrow typed adapter until that declaration reaches the published client package.

See DESIGN.md for the interaction contract, security boundary, compatibility approach, and verification strategy.

License

MIT