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

@brdgkr/codex-handoff

v0.1.5

Published

Project handoff and cross-machine resume workflow for Codex.

Vulnerabilities

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

Links

Git

Maintainers

ideookideook

Keywords

codexhandoffsyncclicloudflare-r2developer-tools

Readme

codex-handoff

Keep Codex work portable across machines, repos, and sessions.

node >=18 backend cloudflare r2 platform macOS windows license mit

codex-handoff watches repo-related Codex sessions, builds repo-scoped handoff memory under .codex-handoff/, and syncs that state to a remote backend so you can resume on another machine with the right context already in place.

Codex is OpenAI's coding agent. OpenAI describes Codex as "a coding agent that helps you build and ship with AI—powered by ChatGPT" and the Codex app as "a command center for agentic coding." Download and learn more at openai.com/codex or read Introducing the Codex app.

Start With Codex

codex-handoff is built for repo-scoped, one-person handoff across machines. It keeps pulled thread state under .codex-handoff/synced-threads/, keeps local pushable thread state under .codex-handoff/local-threads/, and can run background sync while Codex is open. It can also keep a compact repo-level memory file at .codex-handoff/memory.md so new sessions can start from a short summary before drilling into synced thread detail.

Open the Codex app in the project you want to manage, make sure that project is the current workspace/cwd, and paste one of these prompts into the Codex chat. Use the same setup-and-start prompt on another PC. Plain setup already decides whether this repo should pull remote state or push local state.

Install if needed, then set up and start:

Install or upgrade `@brdgkr/codex-handoff` with npm if needed, then set up codex-handoff for this repository and start the agent.
Finish only when setup has completed and the agent is running.

Set up and start when the package is already installed:

Set up codex-handoff for this repository and start the agent.
Finish only when setup has completed and the agent is running.

Set up this repo without starting the agent yet:

Set up codex-handoff sync for this repository, but do not start the agent yet.

Remote Backend

The first supported backend is Cloudflare R2.

After the npm package is installed, setup needs valid R2 credentials for the current repo. The two simplest auth paths are:

Prompt-friendly auth path:

codex-handoff remote login r2 --from-clipboard
codex-handoff setup

File-based auth path:

codex-handoff remote login r2 --dotenv ~/.codex-handoff/.env.local
codex-handoff setup

Common Tasks

  • Set up one repo and start background sync. Use a Codex prompt or run codex-handoff setup.
  • Run a one-shot sync without relying on the background agent. Use codex-handoff sync now.
  • Inspect or rebuild repo context when you need to understand current handoff state. Use codex-handoff status, codex-handoff sync status, codex-handoff resume, and codex-handoff search.
  • Update the optional repo-level memory summary. Use codex-handoff memory summarize.
  • Stop managing the current repo without deleting its cached data. Use codex-handoff detach.
  • Remove local handoff files from .codex-handoff/ while keeping credentials. Use codex-handoff purge-local and codex-handoff purge-local --apply.
  • Delete one repo's remote backup from Cloudflare R2. Use codex-handoff remote purge-repo --repo-slug <slug> and add --apply to execute it.
  • Stop or disable the background service on this machine. Use codex-handoff agent stop and codex-handoff agent disable.

What It Stores

The repo-local state is intentionally simple:

  • .codex-handoff/synced-threads/ pulled thread payloads used for default restore reads, including current-thread.json, thread-index.json, and threads/
  • .codex-handoff/local-threads/ local thread payloads prepared for push
  • optional derived files such as .codex-handoff/memory.md manually generated repo memory artifacts that are not part of the default bootstrap read path. The current format keeps a stable repo summary near the top and appends timestamped conversation updates when new synced thread activity arrives.

Machine-local config and R2 credentials live under ~/.codex-handoff/.

For quick orientation, read .codex-handoff/memory.md first when it exists. For detailed restore reads, stay inside .codex-handoff/synced-threads/: start with current-thread.json, then use thread-index.json to decide which specific bundle under threads/ to inspect next.

Docs

License

MIT