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.
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.
Tracking leftover dev servers and watchers by Claude Code session is really useful. Can seshka distinguish processes still being used by another active session before terminating them, especially when multiple sessions share the same project?
Leftover dev servers holding ports happen to me daily with several Claude Code sessions running in parallel. Grouping them by the session that started them is the right view. Does it treat processes started inside a git worktree as part of the same session, or does each worktree show up on its own?
grouping by session id is the clever part. does the auto end for idle sessions also clean up the servers they left running, or just the session itself?
such a simple but useful idea! i actually struggle more with disk space than leftover processes. old worktrees and caches keep piling up on my Mac. Any plans to tackle those too? congrats on the launch!
Such a great use-case! Wish I could try it out on Linux though. I always forget to stop my dev servers, and it ends up making my computer super slow.
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?
Old dev servers from closed sessions holding onto ports is a weekly thing for me. Any chance of a Windows version?
This is the exact tax I pay for running a lot of Claude Code sessions — I usually only find the orphaned dev server when something else tries to grab its port. Grouping leftovers by session, with memory and ports, is the part that makes this usable for me; killing by port alone is always guesswork. The auto-end for idle sessions is what I'd turn on first. Congrats on the launch — native Swift and MIT is a great combo for a tool like this.
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!
Congrats on the launch!
This app is a great example of the saying "Do one thing and do it well"
leftover processes grouped by session with memory and ports, so useful. congrats Miodrag!
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?
About seshka on Product Hunt
“Kill what Claude Code left behind”
seshka launched on Product Hunt on November 17th, 2026 and earned 138 upvotes and 36 comments, placing #9 on the daily leaderboard. 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.
seshka was featured in Mac (103.9k followers), Open Source (69.1k followers), Developer Tools (523.3k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 159.2k products, making this a competitive space to launch in.
Who hunted seshka?
seshka was hunted by Miodrag Todorovic. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how seshka stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
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.