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

terminus-shell

v0.1.7

Published

Agent-friendly persistent remote shell: SSH exec, durable tmux sessions, cursor-based output reading, and per-server memory for AI agents.

Downloads

1,144

Readme

terminus-shell

Agent-friendly persistent remote shell. SSH exec, durable tmux sessions, cursor-based output reading, and per-server memory — designed for AI agents, usable by humans.

npm install -g terminus-shell
terminus setup            # install the agent skill into Claude Code / Codex

Why

Most shell tools give agents one-shot command execution. Terminus gives them a durable workspace:

  • Persistent sessions — a session maps to a remote tmux session; cwd/env survive across calls, disconnects don't destroy state.
  • Cursor readsread --from-cursor returns only new output since last read; long tasks become fire-then-poll.
  • Per-server memory — agents store and recall facts about servers (deploy paths, quirks, task state) across conversations.
  • Stable --json everywhere; remote exit codes pass through.
  • Connection daemon — repeated calls reuse a pooled SSH connection (~0.6s instead of ~2.3s); the daemon exits itself after 5 idle minutes and never leaves processes behind.

Quick start

terminus key add mykey --kind rsa --private-file ~/.ssh/id_rsa
terminus server add prod --host 1.2.3.4 --user ubuntu --key mykey

terminus exec prod -- uname -a                  # one-shot (no tmux needed)
terminus exec prod:work -- cd /srv/app          # persistent session
terminus exec prod:work -- docker compose ps    # same cwd as previous call

terminus write prod:work -- "./deploy.sh 2>&1"  # fire and forget
terminus read prod:work --from-cursor --json    # collect new output later

terminus memory add prod --key deploy_dir -- "app lives in /srv/app"
terminus memory ls prod --json                  # recall before acting

Agent integration

terminus setup installs the skill for Claude Code and Codex (user-wide). Project-local targets:

terminus setup cursor windsurf agents   # .cursor/rules, .windsurf/rules, AGENTS.md

Platform

Windows x64 (prebuilt, zero dependencies — SQLite and libssh2 are compiled in). Linux/macOS planned.

Currently no known-hosts verification and keys are stored unencrypted locally — treat it as a dev tool, not a production credential store, until those land.

License

MIT