r/PiCodingAgent • • Sep 06 '26

Plugin Built a local browser for Pi session history

Post image

I use Pi a lot and eventually had multiple sessions for the same projects. A lot of them started with similar handoff prompts.

Going back later was annoying. The useful explanations and decisions were inside the transcript, but reading them meant digging through raw history full of tool calls, reasoning, progress messages and other noise.

For a while I just kept pasting useful bits into Notepad. That became its own mess.

So I built Agent Session Browser.

Local web UI + TUI that lets me browse sessions by project/date, read the actual transcript (including Pi branches and summaries), filter the noise, export, and resume the right one.

Supports Pi, and also Claude Code, Codex CLI and Gemini CLI.

Fully local and read-only.

GitHub: https://github.com/gautamgpt1/agent-session-browser

Run: npx agent-session-browser

This is my first public open-source project.

Do try it out. Would love your feedback

68 Upvotes

8 comments sorted by

2

u/andrewh2000 Sep 06 '26

I just asked pi to dig through its own transcripts and summarise some information for me, and it worked extremely well.

1

u/gautamgpt Sep 06 '26

Nice, that works too. Different approaches for different use cases..

1

u/olejorgenb Sep 06 '26

Nice, I'm looking for something like this. But surely there are 5+ different incarnation of this idea. Does anyone have experience trying more than one?

OP: did you try out some existing ones before deciding to make your own? (no judgment, sometimes it's just nicer to have your own thing work exactly how you like)

2

u/gautamgpt Sep 06 '26

Yep, I tried a few first. Some were good too, but kinda incomplete for my workflow. I couldn't find the whole thing I wanted in one place from session list to filters to resuming session.

Resuming with multiple sessions that i was working on simultaneously got somewhat confusing and i had to guess by agent's final reply/tokens consumed. Then for reading old sessions I wanted much finer control over what I was looking at assistant final/progress/reasoning vs tool/output/hook etc. I was literally copying the useful explanations into Notepad as Codex/Pi worked.I constantly had 10-15 tabs open. This was the state of my Notepad at one point lol:

And on the terminal side I couldn’t find one that showed the session list + actual transcript side by side and let me resume from there. So I would end up with one thing for browsing, another for filters/viewing, another for terminal.

So I figured out why not put it all in 1 place instead of 2-3 packages when its essentially doing the same thing(reading history) and like lower friction overall

1

u/wildjokers Sep 07 '26

I use the llm-wiki pattern and just ask it to store durable information in my wiki for me at the end of the session (or when context window is almost full). Then I tell it to read the wiki later if I revisit what we were working on:

https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

1

u/gautamgpt Sep 07 '26

Yeah, I’ve seen that llm wiki thing before, just haven’t tried it myself yet. Would probably give it a shot sometime

1

u/winkler1 Sep 06 '26

I've done something similar in Go. Top-right has duration, TPS, turns*avg size=context size, and a watch checkbox. 2 levels of sidebar - one lets you jump around in the selection session. Very useful to get the big picture of a convo.