omp packages

pi-handoffs1.0.0

Session handoffs for pi: a deliberate alternative to compaction — detailed recent context, a task list that has you ready to go, and a permanent work log. Never-deleted, numbered documents in ~/.pi/handoffs/.

andrewprock Published 7 days ago MIT ~325 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

pi-handoffs

A pi extension for session handoff management: durable, numbered handoff documents that let any new session resume your work without the old conversation.

Handoff files live in ~/.pi/handoffs/ (plus repo roots) and are never deleted — they accumulate as a permanent record of how each project evolved. Nothing is loaded automatically at startup; a handoff enters the session only when you explicitly load it.

Why handoffs instead of compaction

A handoff is a deliberate alternative to letting compaction summarize your session for you:

  • It takes the place of a compaction — instead of a lossy machine summary, you get a document written on purpose, with the agent and user deciding what matters.
  • It keeps recent context in detail — how things work now, exact status, what was decided this session and why — not a compressed approximation.
  • It lists issues and tasks in priority order, so the moment a handoff is loaded into a fresh session you are ready to go at the top open task, not re-deriving state.
  • It serves as a work log — numbered, dated, never deleted, so the documents accumulate into a permanent record of the project's evolution that any future session can consult.

Commands

/handoff                  Interactive subcommand menu
/handoff write            Write HANDOFF<n+1> via the publishing workflow
/handoff list             List all documents, most recent last
/handoff read <doc>       Load the specified document (number, "handoff 9",
                          filename substring, or full path)
/handoff restore          Load the most recent document for this project
/handoff now              Write, start a new session, load the most recent
/handoff help             Show the help text

How it works

  • /handoff write sends the agent a structured publishing workflow: reconstruct ground truth (git status, latest handoff, findings), clarify open questions, then write <dirname>-<YYYY-MM-DD>-<HHMMSS>-HANDOFF<n+1>.md (time in 24-hour HHMMSS, so same-day handoffs stay distinct and ordered) with sections for current pipeline state, how things work now, the active program, a prioritized task list, deferred queue, and standing invariants.
  • /handoff restore / read inject a resume message: the handoff's task list headlines plus the suggested next-session opening, so the new session picks up at the top open task instead of re-deriving state.
  • /handoff now chains it all: wait for idle → write → verify a new document appeared → start a new session → load it. One command from "we're done here" to a primed fresh session.
  • Project scoping: handoffs match by hyphenated directory name prefix, so /handoff restore and list know which documents belong to the repo you're in (* marks the current project, → marks the loaded one).

How this differs from pi-handoff

pi-handoff generates a quick note from the current session and starts a new one. pi-handoffs treats handoffs as permanent project documents: numbered, dated, never deleted, format conventions carried forward from the previous handoff, with explicit task lists and invariants — designed for long-running projects that accumulate history across many sessions.

Install

pi install npm:pi-handoffs

or from git:

pi install git:github.com/andrewprock/pi-handoffs

License

MIT