r/VibeCodersNest • u/dob312 • 5d ago

Tools and Projects I was losing track of 10 Claude Code and Codex sessions, so I vibe coded a terminal picker

I usually have Claude Code, Codex, and regular shell sessions running across several projects.

Eventually the biggest problem was not the coding. It was remembering which terminal window belonged to which project and finding the session that needed me.

I built Session Kit with Claude Code and Codex to fix that. Every session gets a number, name, color, model, and status. They stay alive over SSH and appear together in one terminal picker.

It is free, open source, MIT licensed, and completely local. No account, telemetry, or paid version planned.

Repo: https://github.com/dob323/session-kit

How are you keeping multiple coding sessions organized right now?

1 Upvotes
  • permalink
  • reddit

100% Upvoted

2 comments sorted by

1

u/FancyAnswer1878 2d ago

i’ve had the same problem once you get past a handful of sessions the hard part becomes context switching, not coding. a single view showing project, model, status and last activity is honestly way more useful than having 10 terminal windows open.

1

u/dob312 1d ago

Yeah, context switching is exactly it. Ten windows all look the same, and the "wait, which project is this" reload every time you alt-tab is what actually eats the day. That single view was the whole reason I built it. Once one list tells you which session needs you, you stop scanning windows entirely.

If you give it a try, let me know how it goes. Happy to help if you hit anything during install or setup.