v0.3.2 — the plugin loads again

A real Chrome or Edge for the agent to work in, mirrored in the sidebar so you can watch and take over. Every conversation gets its own browser with its own sign-ins — nothing else to install, it drives the Chrome or Edge already on the machine.

dsh plugin --profile web add @cjylzs/dsh-browser

From a tag instead of the registry:

dsh plugin --profile web add github:CJYLZS/dsh-browser#v0.3.2

Desktop:

"<Desktop install dir>/resources/runtime/cli/bin/dsh.cmd" plugin --profile desktop add @cjylzs/dsh-browser

Restart the harness after installing. Needs a dsh on 0.1.7-rc.1 or later, and a Chrome or Edge already installed; playwright-core is a dependency and downloads no browser of its own.

What changed since v0.3.1

• The plugin loads again. The harness keys every client boot row by package.json's name, and the client bundle registers itself through window.__ModuleLoader__.load({ id }) against that key. v0.3.0 renamed the package to @cjylzs/dsh-browser but the build kept registering dsh-browser, so the script ran, the row stayed unregistered, and the whole plugin failed to import: web boot: 1 entry did not activate / client-modules: could not load "@cjylzs/dsh-browser" (#2). This was not Linux-specific — every 0.3.0 and 0.3.1 install had it.
• The id now comes from package.json instead of a hand-written constant, and test/artifact.test.ts runs the built bundle and pins the registration id to the package name, so a rename cannot silently desync them again. The built artifact is checked, not just the config.

Upgrading

If the profile recorded a caret range (^0.3.1), update moves it:

dsh plugin --profile web update @cjylzs/dsh-browser

If it recorded an exact version, name the new one:

dsh plugin --profile web add @cjylzs/dsh-browser@0.3.2

There are no configuration changes — this fixes the shipped artifact only.

v0.3.1 — on npm, and the install line runs

A real Chrome or Edge for the agent to work in, mirrored in the sidebar so you can watch and take over. Every conversation gets its own browser with its own sign-ins — nothing else to install, it drives the Chrome or Edge already on the machine.

dsh plugin --profile web add @cjylzs/dsh-browser

From a tag instead of the registry:

dsh plugin --profile web add github:CJYLZS/dsh-browser#v0.3.1

Desktop:

"<Desktop install dir>/resources/runtime/cli/bin/dsh.cmd" plugin --profile desktop add @cjylzs/dsh-browser

Restart the harness after installing. Needs a dsh on 0.1.7-rc.1 or later, and a Chrome or Edge already installed; playwright-core is a dependency and downloads no browser of its own.

What changed since v0.3.0

• The install command in the READMEs runs. It was dsh plugin add --profile web <spec>, which the CLI rejects with required option '--profile <name>' not specified — the profile comes before the verb. Corrected in both READMEs, in the version table, and in the local-checkout line.
• The plugin is on the npm registry as @cjylzs/dsh-browser, so installing no longer needs a git spec. A tag install still works and still needs no build step: the built lib/ is committed with every tag.
• repository.url is the form npm itself writes back (git+https://…), so registry consumers and the plugin-market probes see the same value.

Why 0.3.1 and not a re-publish of 0.3.0

npm does not allow publishing over a version that already exists, and 0.3.0 went out carrying the broken install line. 0.3.1 is the first version whose README can be followed literally.

v0.2.6 — a real browser per conversation, mirrored in the sidebar

A real Chrome or Edge for the agent to work in, mirrored in the sidebar so you can watch and take over. Every conversation gets its own browser with its own sign-ins — nothing else to install, it drives the Chrome or Edge already on the machine.

dsh plugin add --profile web github:CJYLZS/dsh-browser#v0.2.6

Desktop:

"<Desktop install dir>/resources/runtime/cli/bin/dsh.cmd" plugin --profile desktop add github:CJYLZS/dsh-browser#v0.2.6

Restart the harness after installing. Needs a dsh on 0.1.7-rc.1 or later, and a Chrome or Edge already installed; playwright-core is a dependency and downloads no browser of its own.

What changed since v0.2.5

• Installing from the Plugins page is documented, and the Desktop CLI line sits next to it.
• package.json declares engines.dsh, so a market's compatibility check reads the supported dsh range instead of inferring one from peer dependencies.
• The one-line description says what the plugin does rather than how many tools it ships.

Installing from a tag

The built lib/ is committed with every tag, so an install needs no build step. The profile's package.json records the ref you chose; to move versions, re-add with the new ref.