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

dsh-windows-parallel-mcp

v0.1.2

Published

Drive a Windows window without moving the cursor or stealing the keyboard: one tool, five actions, a channel decision table that prefers the quiet door, and a bounded self-reversing focus flash when only UI Automation can reach the control. Windows PowerS

Readme

dsh-windows-parallel-mcp

0.1.2 — every real click now carries its own disturbance proof. The name was reserved earlier under a weaker claim (see CHANGELOG.md); the claim below is the measured one. 0.1.1 is 0.1.0's behaviour with a corrected packaging chain; 0.1.2 adds the runtime proof chain — wpm click returns a proof= verdict and proofDimensions, measured against the desktop around your own call.

A DSH plugin that lets an agent drive its own Windows windows without moving your cursor. Where a window accepts a window message, you never lose focus at all. Where it only exposes UI Automation, you lose focus for one bounded flash that is reversed automatically. Everywhere else it refuses, with a code and a reason.

Not affiliated with dsh-windows-mcp. Different plugin, different trade-off: that one is a carrier bundle with a broad tool surface; this one is a single action tool whose entire design is about not disturbing the desktop.

What it does

One tool, five actions:

| action | what it returns | |---|---| | windows | live windows that can be driven: hwnd, title, class, pid, rect | | status | what currently holds the foreground and the keyboard focus, and whether the engine is paused | | click | click at a screen coordinate inside the named window | | type | write text into the target (a classic edit child, or a named UIA element) | | focus | move keyboard focus to a named control inside the target |

The engine picks the cheapest available door per call:

  • quiet tier — a classic child window receives the click/text as a window message. Measured: 0 foreground changes in 6 of 6 rounds, effect verified by the app's own state, cursor moved 0 px.
  • bounded-flash tier — only UI Automation can reach the control, which raises the target. The engine records the focus table before acting, reverses it once afterwards, and never pulls focus from a window you chose. Measured net return 15–95 ms from three independent measurements (the 120 ms budget was never approached).

What you see while it works

After a successful click a small marker is placed at the point that was clicked. It is a click-through, always-on-top window with WS_EX_TOPMOST | WS_EX_NOACTIVATE | WS_EX_TRANSPARENT: measured that Show() does not change GetForegroundWindow, that WindowFromPoint at the marker's centre returns the window underneath, and that a real click through the shipped plugin puts the marker over the point it hit (physical pixels; the process declares DPI awareness, because using WPF's device-independent units put the marker at half scale on a 150% display). It hides itself 1.5 s after the last placement. Cost: ~19 ms per placement, fired after the action has already answered; the first action pays a one-time ~875 ms while the overlay starts.

The pause key is not a fixed key. Ctrl+Alt+Q is the first candidate, but it can already be owned by another app — on the machine this was measured on it was (Win32 1409), and seven of the other eight measured candidates were free. The engine walks a candidate list, registers the first free chord, and reports what it actually registered in status as pauseHotkey=.... It never silently claims the documented key works. overlay=true in settings controls the marker; the pause flag itself is engine-side and refuses actions with paused.

Refusals are a normal result, not an error: no_hwnd, paused, elevated_target, unreachable, terminal_no_door, needs_facts, action_failed, restore_failed. Each carries a reason and a next step — see docs/refusals.md.

Every real click carries its own disturbance proof. click returns a proof=pass|inconclusive|… verdict plus a proofDimensions field (cursor / foreground / focus). Around your call the engine samples cursor position, foreground window, keyboard focus and last-physical-input age — in a short pre-action control window (when, by construction, nothing was running) and inside the settle wait it already pays. The judgment is one pure function (lib/proof-window.mjs, unit-tested against 32 synthetic windows whose answers are known by construction). What it honestly can and cannot say: a switch of foreground on a quiet tier fails — the control shows the desktop was not doing it, so it is the action's to explain; a cursor jump is reported, never accused, because with nothing running this desktop's cursor showed multi-gap unexplained motion on its own (a re-runnable probe ships: scripts/idle-baseline.mjs). The cursor promise therefore lives where blame is decidable: a build gate asserts no shipped file contains SetCursorPos/SendInput/mouse_event/keybd_event, so a regression that adds cursor control fails at build time with certainty instead of being hunted at runtime among ambient motion.

What it does not do

  • No synthetic input. There is no physical option: it is absent from the schema, not disabled by default. No SendInput, no keybd_event, no mouse_event.
  • No forged-Alt foreground trick. That route works and other plugins use it, but it injects a real key event — a keystroke you make in that window can land in whichever window the trick just raised.
  • No OCR / Set-of-Marks / pixel fallback. Not part of this claim, and already done well elsewhere.
  • No watchdog. The restore is one-shot and happens inline. A watchdog that keeps chasing the foreground would fight you.
  • Terminals are refused (terminal_no_door): their text surface exposes neither a child window nor a Document element. That is the target a developer most wants driven quietly, and it is the one that cannot be.

Install

dsh plugin --profile <profile> add dsh-windows-parallel-mcp

Requires Windows with Windows PowerShell 5.1 (it ships with Windows) — no Python, no uv, no MSVC runtime, no native module. The engine is a PowerShell sidecar started lazily on the first tool call, not at plugin load.

engines.dsh is an explicit two-sided range. There is no runtime version probing and no silent degradation.

Settings

| key | default | effect | |---|---|---| | enabled | true | server-side gate: when off, every action refuses with paused before the engine is reached | | settleMs | 350 | how long the app gets to commit state before the effect is judged | | requestTimeoutMs | 20000 | a worker that stops answering is killed and restarted on the next call | | powershellPath | "" | override the interpreter (pwsh accepted) | | logWorkerStderr | false | forward worker diagnostics to the host log |

What measurement established

The hard gate was run on a real Windows desktop before any of this shipped, and part of the original goal statement did not survive it. Kept here rather than quietly dropped:

  • Cursor: true. Every channel tested produced 0 px of cursor displacement across 24 action rounds, against a control arm that made no call.
  • "Keyboard focus never changes": false as a general property. UIA pattern actions raised their own target in 12/12 and 6/6 rounds with no mouse button down, no modifier key down and the cursor outside the target rect; a no-call control arm raised 0/6 in the same conditions.
  • Window messages: true but narrow. 6/6 effective, 0/6 raising. But a message needs an address: only 17 of 57 live windows here have one, and the two largest families (UWP/WinUI, Chromium/Electron) have none.
  • The complementary-exclusive catch: on the toolkit where messages work (WinForms/classic), UIA exposes no patterns at all; on the toolkits where UIA works (WPF/UWP/Chromium), there is no message door. The identifiable door and the quiet door are never on the same window.
  • Restoration is measured, not assumed. After a raise, the widget that held focus came back 6/6 and 6/6 in two independent runs, and internal focus (not just the window) returned 4/4.
  • The engine is often quieter than the budget suggests. Under its real operating condition, UIA Invoke was foreground-neutral in 0 of 12 rounds — the earlier 6/6 and 12/12 were measured under a construction that first took the foreground away. The flash tier is a fuse, not a promise of disturbance.

elevated_target is measured live: the engine compares the target's integrity RID against its own and refuses before acting (verified on an elevated Task Manager; 19 medium windows, zero misrefusals). The restore-failure path on an elevated target (restore_failed) remains unmeasured end-to-end and is stated as such in docs/refusals.md.

License

MIT