pi-auto-handoff

Automatic session checkpoints and explicit fresh-session continuation for Pi

Packages

Package details

extension

Install pi-auto-handoff from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:pi-auto-handoff

Package: pi-auto-handoff
Version: 0.1.1
Published: Oct 13, 2026
Downloads: 358/mo · 26/wk
Author: dpaluy
License: MIT
Types: extension
Size: 100.1 KB
Dependencies: 0 dependencies · 2 peers

Pi manifest JSON

{
  "image": "https://raw.githubusercontent.com/dpaluy/pi-auto-handoff/master/handoff-preview.png",
  "extensions": [
    "./src/index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-auto-handoff

Version 0.1.1. Changelog.

Save work checkpoints after inactivity or high context use. Continue in a linked fresh Pi session when ready.

Handoff loaded in a linked fresh Pi session (offline demo)

Install

Requires Pi 1.0.4 or later and Node.js 22.19 or later.

pi install npm:pi-auto-handoff

Or install from GitHub:

pi install git:github.com/dpaluy/pi-auto-handoff

Restart Pi or run /reload.

Use

Command	Action
`/handoff`	Save a checkpoint.
`/handoff status`	Show checkpoint status.
`/handoff continue`	Refresh if needed, start a linked fresh session, and continue immediately.

Checkpoints are saved in Pi's session file, not project files. The original session remains available through /resume. Native compaction and cache warming are unchanged.

Automatic checkpoints

Defaults: 50 idle minutes or 70% estimated context use. Automatic checkpoints run in TUI and RPC modes with saved sessions. Session replacement always requires /handoff continue.

Change thresholds when starting Pi:

pi --handoff-idle-minutes 30 --handoff-context-percent 80

Set either value to 0 to disable that trigger.

Each checkpoint request has a 120-second timeout. On timeout, the extension aborts the request and retries once after 5 seconds, only if the first request has stopped and the session is still idle and unchanged. New input or session/model changes cancel recovery. If the provider does not stop during backoff, recovery fails without starting another request; later attempts stay blocked until it stops. Other failures are not retried.

Privacy

Checkpoint generation sends bounded session text to the active model provider. Provider charges or subscription limits can apply. Notes can contain sensitive information; secret removal is not guaranteed.

License

MIT

Supported by Majestic Labs.