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

@helgesverre/resume

v0.1.0

Published

Search and resume local coding-agent sessions across many tools from one searchable TUI.

Readme

--resume

Search and resume local coding-agent sessions across many tools — after a crash, a closed terminal, or a context switch.

resume in action — searching, expanding the preview, cycling the agent filter, toggling timestamps, and copying a cd-restoring resume command

resume scans the session histories that your coding agents leave on disk, normalizes them into one searchable list, and prints a cd-restoring command you can run to jump straight back into the right conversation in the right directory.

Usage

resume

Type to search by tool, title, cwd, session id, or preview text.

| Key | Action | | ---------------- | ------------------------------------------------------------ | | type | Filter by tool, title, cwd, id, or preview | | / | Move selection | | PageUp/Down | Jump 10 rows | | Tab | Expand / collapse the preview panel | | Ctrl+A | Cycle the agent filter (all → one tool → …) | | Ctrl+T | Toggle an exact yyyy-mm-dd hh:mm:ss column | | Backspace | Delete a search character | | Ctrl+U | Clear the search | | Enter | Copy the resume command to the clipboard, print it, and exit | | Esc / Ctrl+C | Quit without printing |

Pressing Enter copies the command to your clipboard and prints a cwd-restoring command such as:

cd /path/to/project && claude --resume SESSION_ID

To run it directly, evaluate the output:

eval "$(resume)"

Supported tools

resume reads each tool's local session files (no network access) and knows how to build the right resume command for each:

| Tool | Scanned location | Resume command | | ----------- | --------------------------------------------------------------------------------- | ---------------------------------- | | Claude Code | ~/.claude/projects | claude --resume <id> | | Codex | ~/.codex/sessions, ~/.codex/archived_sessions, ~/.codex/session_index.jsonl | codex resume <id> | | Amp | ~/.local/share/amp/threads | amp threads continue <id> | | OpenCode | ~/.local/share/opencode/storage | opencode --session <id> | | Junie | ~/.junie/sessions | junie --resume --session-id <id> | | Pi | ~/.pi/agent/sessions | pi --session <id> | | Kimi | ~/.kimi-code/session_index.jsonl, ~/.kimi-code/sessions | kimi --session <id> | | Copilot | ~/.copilot/session-state | copilot --resume <id> | | Antigravity | ~/.gemini/antigravity-cli/conversations, ~/.gemini/antigravity-cli/brain | agy --conversation <id> |

When a session records its working directory, the printed command is prefixed with cd <cwd> && so you land back in the project. Parsed sessions are cached in ~/.cache/resume/sessions-cache-v2.json, keyed by file size and mtime, so repeat runs are fast.

Other commands

resume --json        # print normalized sessions as JSON
resume --copy <id>   # copy the resume command for an exact or prefix session id to the clipboard
resume --help        # show usage and keybindings

When stdout is not a TTY (e.g. piped), resume prints up to 50 sessions as tab-separated tool<TAB>id<TAB>title<TAB>command rows instead of opening the picker.

Build

npm install   # also runs `npm run dist` via the prepare script
npm link      # exposes the `resume` binary (dist/resume.mjs)

Development

npm run build         # compile ReScript (src/*.res -> lib/)
npm test              # build, then run the ReScript test suite
npm run dist          # build + bundle to a single dist/resume.mjs
npm run format        # format the ReScript sources with `rescript format`

The application is written entirely in ReScript (src/*.res):

  • src/Session.res, src/SessionList.res — the session model, resume-command builder, search, and JSON codecs.
  • src/adapters/*.res — one module per tool, plus shared AdapterUtil/Codec helpers; registered in src/Adapters.res.
  • src/Cache.res — the stat-keyed parsed-session cache, with explicit per-adapter encode/decode codecs.
  • src/Tui.res — a pure core (update, view, keyOfEvent) wrapped by a thin effectful picker shell, so layout and key handling are unit-tested without a TTY.
  • src/node/*.res — thin typed bindings to Node's fs, path, process, readline, and url.
  • src/Main.res — the CLI entry point.

ReScript compiles to lib/, and esbuild bundles lib/es6/src/Main.mjs into the single executable dist/resume.mjs (with clipboardy kept external). ReScript files are formatted with rescript format.

Demo GIF

demo/resume.gif is recorded with VHS. It runs against a throwaway tree of synthetic sessions (one per supported tool) so the recording never shows real history. To regenerate it:

vhs demo/resume.tape   # writes demo/resume.gif

demo/resume.tape builds the fixtures first (demo/make-fixtures.mjs, into the gitignored demo/home/) and points HOME at them. The picker treats every printable character as filter input — toggles are bound to Ctrl-modified keys (Ctrl+T time, Ctrl+A agent cycle, Ctrl+U clear) and Tab expands the preview — so the demo's search terms can contain any letter.