Your messages
What you asked for, and how you steered the work.
A Pi extension for long sessions
Rarebit picks out your messages and the agent’s prose replies. Those few lines carry your intent, the progress, and where the agent stopped. Tool traffic stays out, and the source session stays untouched.
Next: review the fix before accepting it.
tool traffic · still in the source sessionChapter I
Catch up
What you asked for, and how you steered the work.
What the agent said it would do, turn by turn.
The agent’s last word before it waited for you. A stop is not proof that the work is right.
Chapters II–IV
What the rare bits are for
Remind the agent
Hand the rare bits back to the agent before its next turn. Rarebit writes them to private local files and sends one request that points the agent to them.5
/rarebit recall <request>Catch up yourself
Ask your model for a short Summary of the rare bits, then read it in Pi with Recap. Summary is optional and needs a configured model.4
/rarebit summarizeStart fresh
Start a new session from the newest rare bits that fit a size budget, with the tool calls left behind. It does not promise complete context transfer.6
/rarebit forkInstall
pi install npm:@hypercarrier/rarebit@0.2.0
Rarebit is public alpha software for Node 22+ and Pi 0.83+. After a restart, ask Pi to recall what matters: /rarebit recall What should guide the next turn?
Recall sends your model provider what the agent reads. Read the privacy guidance.
npx --package @hypercarrier/rarebit@0.2.0 rarebit extract --session <path-or-session-id> --json
Session files live under ~/.pi/agent/sessions/. A Session ID also works.
src/rarebit-core.mjs:selectRarebitsREADME.md#privacy-and-local-datasrc/rarebit-core.mjs:rarebitMetadataREADME.md#configure-optional-derivationsREADME.md#2-recall-for-the-agentREADME.md#3-fork-as-a-distilled-native-fork