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

@funtusov/heartbeat

v0.1.1

Published

Codex thread heartbeat CLI (auto-continue long tasks)

Downloads

158

Readme

@funtusov/heartbeat

Codex thread heartbeat CLI with local job tracking.

It periodically checks a Codex thread via codex app-server, and when the latest turn is terminal (completed, interrupted, failed) it starts a follow-up turn with your continuation prompt.

Install

npm i -g @funtusov/heartbeat
heartbeat --help

Or run without installing:

npx @funtusov/heartbeat --help

Requirements

  • codex CLI installed and authenticated (codex login)
  • Node.js >= 18

Commands

Start a background heartbeat

heartbeat start --thread-id 019c... --interval 15m --for 8h

Show active/history jobs (table)

heartbeat status

Columns include:

  • STARTED
  • EVERY
  • THREAD
  • RUNS (times ran)
  • LAST RUN
  • NEXT RUN
  • LAST ACTION

Stop one/all jobs

heartbeat stop <job-id>
heartbeat stop --all

View job logs

heartbeat logs <job-id>
heartbeat logs --tail 50

Clear old non-running jobs

# Remove stopped/failed/exited/completed jobs and their logs
heartbeat clear

# Preview first
heartbeat clear --dry-run

# Only clear jobs older than 7 days
heartbeat clear --older-than 7d

Foreground mode (legacy behavior)

heartbeat --interval 15m --until "tomorrow 7am"
# same as:
heartbeat run --interval 15m --until "tomorrow 7am"

Follow-up prompt

Default prompt:

Continue working on this task. Pick the next highest-impact step, execute it, and report concise progress before stopping.

Override with --prompt or --prompt-file.

Notes

  • Multiple concurrent heartbeat jobs are supported.
  • Use --yolo with run/start to launch Codex as codex --yolo app-server ....
  • By default, the first cycle waits one full --interval; --once still runs immediately.
  • Default local state path is ~/.heartbeat (jobs + logs).
  • heartbeat start does a preflight thread/resume check before daemonizing. If a thread id is stale/non-resumable, it fails immediately with remediation guidance.
  • If --thread-id fails to resume, try heartbeat run --once --dry-run without --thread-id to auto-pick a resumable thread in your current --cwd.
  • heartbeat clear only deletes non-running jobs; it does not stop running jobs.