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

omniharness-cli

v0.1.111

Published

OmniHarness — local-first agent orchestration harness for OmniRoute.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dev_angledev_angle

Keywords

omnirouteomniharnessagentsorchestrationcli

Readme

omniharness-cli

OmniHarness — the agent harness built for OmniRoute. Route once, run anywhere: plan, build, research, or turn a swarm loose.

This package ships the interactive terminal UI (Ink/React). The orchestration core and a headless CLI live in the Go source tree.

npm install -g omniharness-cli
omniharness            # launch the TUI in the current working directory

| Command | | |---|---| | omniharness | launch the interactive TUI | | omniharness doctor | check the gateway connection + auth, safely (key is masked) | | omniharness models | list the routing catalog — combos, auto/*, providers | | omniharness update | self-update to the latest npm release | | omniharness --version / --help | version / usage |

Everything else happens inside the TUI.

Connect to OmniRoute

| Variable | Meaning | |---|---| | OMNIROUTE_URL | Gateway endpoint (default http://127.0.0.1:20128) | | OMNIROUTE_API_KEY | Authorization: Bearer <key> on every request — held in memory only, never written to config, sessions, logs, or telemetry | | OMNIROUTE_MGMT_TOKEN | Management token (manage scope) — when set, OmniRoute's MCP tools are discovered and offered to the agent |

If OMNIROUTE_API_KEY is unset, the TUI asks for it on launch and keeps it in memory only. It is redacted from all output.

Inside the TUI

  • Modes (Ctrl+E cycles): plan · build · research · crazy. Crazy mode auto-approves every call and fans an independent plan out across parallel worker agents.
  • Native scrollback is the history — settled turns flow into your terminal's own buffer; the full transcript is restored on exit.
  • Route ribbon — every reply is labelled with the provider it came from; failovers appear inline.
  • Context meter, per-tool cards with diffs, scoped-trust approvals, input queued during a run, Ctrl+Y clipboard copy over OSC 52, session resume, prompt history, /find, /chapters.

Slash commands: /help /clear /sessions /save <name> /forget <name> /attach <files> /find <text> /chapters.

Notes

  • Node.js 20 or newer.
  • Publishing is automatic: every push to main runs .github/workflows/publish.yml, which runs the TypeScript suite, builds, and publishes via npm trusted publishing (OIDC) — no token is stored, provenance is attached automatically. The Go suite gates earlier, on the pull request (.github/workflows/ci.yml). Locally, scripts/release-npm.sh does the same (--dry-run to skip publish; --minor / --major / an explicit version to control the bump).