Launching today

seshka
Kill what Claude Code left behind
123 followers
Kill what Claude Code left behind
123 followers
Claude Code sessions end. The dev servers, watchers and scripts they started don't. seshka shows them in your menu bar, grouped by session, with memory and ports. Kill them in one click. End idle sessions too, by hand or automatically. Free and open source.




Free
Launch Team

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted
Hi Product Hunt, I'm Miodrag from the JigJoy team.
I run a lot of Claude Code sessions. When I close one, the dev servers, watchers and scripts it started often keep running. The day I looked, I had 27 processes from 7 closed sessions holding 5.6 GB of memory, and a handful of ports I kept bumping into.
seshka is the small menu bar app I built to deal with that:
It lists leftover processes grouped by the session that started them, with memory and ports.
One click ends a process, a whole session's leftovers, or everything.
It shows your open sessions with how long each has been idle, and can end idle ones automatically if you turn that on.
It is free, open source (MIT), native Swift, and it only reads what is already on your Mac. Nothing is sent anywhere.
It is not affiliated with Anthropic. I'd love to hear what it finds on your machine, and what you'd want it to do next.
@lotus015 This is great! I look forward to trying it out. Congrats on the launch!
@chris_goodbaudy Thanks Chris! Please do share feedback when you try it out.
@lotus015 Do I need to restart my Mac to see it open? I installed it and double clicked it but then saw nothing happen.
@lotus015 I found it. It's in my top nav bar. The problem I have is when Claude uses Playwright CLI it opens Google Chrome windows and then they never go away until I restart my Mac. Having the ability to kill these unused Chrome windows would be really nice to have as well.
@lotus015 ha, the ones from a worktree I already moved are the worst. the port just stays taken and I have no idea which session started it 😅 grouping by session is the smart bit
Old dev servers from closed sessions holding onto ports is a weekly thing for me. Any chance of a Windows version?
congrats on the launch!
had a dev server answering on 3000 out of a worktree id already deleted. took a while to
work out why the page kept 404ing..
what does it group a process by, and does that hold up after the folder is gone?
@seenew Claude Code leaves hidden flags to each subprocess it spawns, with it's session id, so if we see that session id no longer exists, the processes are still able to be grouped and killed through that. Glad you liked the tool!
the ones that get us are flutter_tester processes from test runs that got cut off. the mac sat at load ~30 on 8 cores one afternoon before we figured out why lol. how do you map a process back to its session once it's double-forked and reparented to launchd?
the ones that get us are flutter_tester processes from test runs that got cut off. the mac sat at load ~30 on 8 cores one afternoon before we figured out why lol. how do you map a process back to its session once it's double-forked and reparented to launchd?
Congrats on the launch! Frankly I was getting tired of copy-pasting the same prompt at the end of merging a PR 😅
I never notice these dead servers and ports until i go to start something and it picks the most random port number because apparently all the other usual ones are still running something. Excited to try this!