npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@collect-flow2/dsh-deeplink

v0.1.0

Published

Start a DeepSeek Harness Web conversation from a URL: /?project=<workspace>&question=<text>.

Readme

URL Deep Link

Start a conversation in the DeepSeek Harness Web UI directly from a URL:

http://127.0.0.1:3080/?project=crawl-next&question=run%20the%20tests

The plugin runs entirely in the browser. It reads the query parameters once, strips them from the address bar, resolves the Workspace, creates a fresh Session in it, reveals it, and sends the question as the first prompt.

Parameters

| Parameter | Required | Meaning | | --- | --- | --- | | question | yes | Prompt text, URL-encoded. Sent verbatim as one text block. | | project | no | Workspace title (exact, case-insensitive) or the last segment of its path (or the full path). Unknown names fall back to the Workspace of the Session currently on screen. | | autosend | no | default on. autosend=0 only leaves the text in the composer draft; nothing is sent. | | preset | no | Agent preset id for the new Session (for example standard, ptc, minimal, cordis). Omit to use the Host default. |

A URL without a non-empty question is ignored completely.

Install

dsh plugin --profile web add -w @collect-flow2/dsh-deeplink

From a local checkout, install the directory instead:

dsh plugin --profile web add -w /Users/halo/Desktop/opensource/dsh-deeplink

Then make sure @collect-flow2/dsh-deeplink is listed in the profile's dsh.profile.bundles (installing through the Plugin Manager page does that, and a running Host reconciles a newly added bundle dependency on its own). The profile's patchReload is live, so the running Host recomposes after the manifest change; refresh the Web page.

The Host serves the browser bundle from /plugins/@collect-flow2/dsh-deeplink/client.js.

Uninstall:

dsh plugin --profile web remove -w @collect-flow2/dsh-deeplink

and drop the bundle from dsh.profile.bundles.

Publish

npm publish

publishConfig.access: public makes the scoped package public on the first release.

How it starts the conversation

  1. readLink(location.search) parses the URL, then history.replaceState strips the query so a refresh does not start a second conversation.
  2. Waits for the workspace and session catalogs (phase === 'ready'), then for the UI's initial Session restoration to settle. Acting earlier would be undone by ui-workspace's own replaceMain.
  3. ctx.sessions.create({ workspaceId, agentPreset? }).
  4. ctx.uiWorkspace.openSession(sessionId) reveals it.
  5. ctx.sessions.using(sessionId, { source: 'deeplink' }, ref => ref.binding.session.prompt([{ type: 'text', text: question }], 'queue')).

With autosend=0 step 5 is replaced by writing the per-Session conversation draft (localStorage['dsh.conversation.<sessionId>']), so the text waits in the composer for a human click.

Security

Autosend is on by default, which means any link can start a prompt in a browser that is already authenticated to this Harness — a link-click CSRF / prompt-injection surface. Mitigations:

  • Keep the server on its default loopback bind; never expose it to a network you do not trust.
  • Use autosend=0 for links you post into chat, docs, or issue trackers.
  • Authentication is still required: a browser without the Web UI session cookie receives 401 and the plugin never runs. Do not append the launch token to a deep link: the token branch 303-redirects to ./ and drops the parameters.

Files

| File | Role | | --- | --- | | package.json | Bundle manifest plus the dsh.client declaration | | cordis.patch.yml | Inserts the deeplink row | | index.js | Empty Host half | | client.js | Hand-written Client bundle (query parsing, navigation, prompt) | | locale/en.json, locale/zh.json | Plugin Manager title and description | | scripts/smoke-test.mjs | VM-based smoke test over a mocked Client Context |

Verification

node --check index.js && node --check client.js
node scripts/smoke-test.mjs

The smoke test loads client.js into a VM with a browser-like sandbox, binds it to a mocked Client Context, and asserts: URL stripping, Workspace resolution by title/path/fallback, Session creation, reveal, prompt content/mode, preset passthrough, autosend=0 draft behavior, and that a prompt rejection is logged instead of escaping as an unhandled rejection.

Browser verification: refresh the Web page, then open a deep link in the same browser. The address bar should lose the query, a new Session should appear in the requested Workspace with the question as its first user message.