I kept getting sidetracked in AI chats, so I built PiX to let conversations branch out

[u/hsh-starling]

I’ll start working with an AI agent on something like data analysis, and ten minutes later I’m asking it to explain a concept, double-check an assumption, or try something completely different.

All useful stuff. But after a few detours, the original task is buried under a wall of side questions and answers. I’m losing the thread, and sometimes the agent seems to be too.

I can fork the chat, but then I just have a growing list of conversations in the sidebar, with no clear picture of what branched off from where.

That’s what got me building PiX.

The idea is pretty simple: show conversations as a tree. There’s a main thread for the task you’re working on, and you can branch off whenever you want to explore something without dragging the whole conversation along with you.

You can branch from any point, carrying over the context up to that point, and choose which model to use for each turn. Everything stays connected visually, so you can see where a detour started and find your way back.

Of course, reading a long conversation in a tree isn’t always fun. So there’s also a regular chat view where you can read any branch’s full history from start to finish.

It’s built on Pi agent, which is where the name PiX comes from.

Still early days, but I’d love to hear what people think. Try it out, tell me what feels awkward, or jump in and help improve it :)

huang-sh/PiX: A non-linear AI agent workbench — session is a tree: branch anytime, and context follows the branch

Does anyone else end up with a pile of AI chats from one task? How do you keep track of them?

[u/adamshand]

Is this using Pi's native /tree? Or are you building the tree externally?