Launched this week

seshka
Kill what Claude Code left behind
154 followers
Kill what Claude Code left behind
154 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

LoomTalk it through in Loom. Ship with AI
Promoted
Congrats on the launch! Frankly I was getting tired of copy-pasting the same prompt at the end of merging a PR 😅
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.
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!
leftover processes grouped by session with memory and ports, so useful. congrats Miodrag!
@mohitvishwakarma Thanks a lot!
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.
@jcbuilds Thanks, glad you enjoyed it!
Congrats on the launch!
This app is a great example of the saying "Do one thing and do it well"
@peckz Thanks Petar! I had to restrain myself from putting too much stuff into it :D
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?
@geekynaman Currently, it treats them all as a part of the same session, but I think this is a very good case to split them, will work on this.
@lotus015 Thanks Miodrag! That would match how I work: one worktree per task, so a group per worktree would tell me exactly which task left what running.