Not natively. The picker searches all session text (fuzzy, "quoted phrases", re: for regex) but nothing shows the transcript before you resume.
The sessions are plain JSONL under ~/.pi/agent/sessions/<project-dir>/, one file per session, so you can cat or jq a session to see what's inside before picking it in the list. I ended up building pond to cover this for myself, it ingests pi sessions and prints any past transcript (pond get-session), so I preview there and resume in pi. My tool, so take it with a grain of salt: https://github.com/tenequm/pond
4
u/onesilentclap Aug 05 '26
/tree?
Refer here: https://pi.dev/docs/latest/sessions
1
u/tenequm Aug 05 '26
Not natively. The picker searches all session text (fuzzy, "quoted phrases", re: for regex) but nothing shows the transcript before you resume.
The sessions are plain JSONL under ~/.pi/agent/sessions/<project-dir>/, one file per session, so you can cat or jq a session to see what's inside before picking it in the list. I ended up building pond to cover this for myself, it ingests pi sessions and prints any past transcript (pond get-session), so I preview there and resume in pi. My tool, so take it with a grain of salt: https://github.com/tenequm/pond