Skip to content

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

Choose a tag to compare

@CJYLZS CJYLZS released this 04 Nov 01:36
· 2 commits to main since this release

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.

The plugin at work: the agent's browser tool calls beside the same browser mirrored in the sidebar

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.