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

@ai-agent-forge/plugin-desktop-windows-input

v0.88.22

Published

Bounded Windows desktop input capability plugin for Agent Forge (desktop_execute and, when the runtime provides replay, desktop_replay)

Readme

@agent-forge/plugin-desktop-windows-input

Bounded Windows desktop input capability plugin for Agent Forge, extracted from the host's src/plugins/desktop (D-075 S3). It registers desktop_execute (one focus/click/type/key/scroll action against an observed UIA target, always followed by a fresh observation) and, only when the injected runtime exposes a replay method, desktop_replay. The shipped production facade intentionally exposes no replay.

The plugin refuses to register any tool when the host runs in readonly mode. On non-Windows platforms importing the package does not throw; tools report an explicit unsupported result instead of probing or falling back to a different driver.

Install

# from a local checkout
agent-forge plugin install ./plugins/desktop-windows-input

# from npm
agent-forge plugin install @ai-agent-forge/plugin-desktop-windows-input

The package ships two manifests: agent-forge.json (ecosystem manifest for the deterministic plugin resolver, platform.os: ["windows"]) and plugin.json (host-load manifest consumed by loadCapabilityPluginFromManifest, entry ./dist/entry.js).

Library surface

import { DesktopWindowsInputAdapter, WindowsUiAutomationDriver } from "@agent-forge/plugin-desktop-windows-input";

  • DesktopWindowsInputAdapter — production input facade (no replay method).
  • WindowsUiAutomationDriver(options?) — PowerShell UIA driver; supports command/timeoutMs/spawnSync/platform injection for brokers and tests.
  • DesktopWindowsAdapter — full-control adapter with replay, carried for host wiring parity with the observe package.
  • createDesktopInputCapabilityFactoryV1(runtime) — registers desktop_execute (and desktop_replay when the runtime provides it) on a CapabilityAPI.
  • Default export of dist/entry.js — the precomposed factory used by external plugin loading.

The UIA adapter code is a deliberate inlined copy shared with @agent-forge/plugin-desktop-windows-observe so both packages stay self-contained.

Development

npm install --ignore-scripts        # repo root, creates the workspace symlink
npm run build                       # plugins/desktop-windows-input (tsgo)
npm test                            # vitest; the entry fidelity test requires `npm run build` first