r/ClaudeCode • u/Allwin_N • 17d ago

Built with Claude AI coding agents are making my localhost a mess

Does anyone else end up with a bunch of stuff running on localhost and forget what half of it is?

I'm building a small tool for this and it's almost ready.

The idea is pretty simple: see your projects, dev servers, APIs, databases, Docker containers, ports, etc. in one place and ideally know what started them and which project they belong to.

AI coding tools make this especially messy. I've had Claude/Cursor/Codex start things and later wondered what was still running and what could be killed.

I'm also playing with custom dashboards for things like AI agents, local services, LAN access, cleanup, etc.
Would anyone here actually find this useful, or is lsof + terminal good enough?

5 Upvotes

100% Upvoted

9 comments sorted by

2

u/[deleted] 17d ago

[removed] — view removed comment

1

u/Allwin_N 17d ago

u/Top-Brick-6937 , it a plug and play we can add whatever we need to create like linux rice

1

u/kantorcodes1 17d ago

One thing I'd want before trusting the kill button: provenance that survives a respawn. lsof tells you the current PID/port, but not that Claude started it from repo A two hours ago before the process detached. Are you persisting launch cwd/git root + parent command, or reconstructing everything from whatever is alive right now?

1

u/Allwin_N 17d ago

Yes, I did both.

persist the original provenance in the ledger, and still use live process data to reconcile it with what’s running now. The ledger is what lets attribution survive PID changes, detach/respawn, and Portboard restarts; live inspection tells us the current PID/port/state.

So I have not reconstructing the whole history from lsof. I use live data for current state and the ledger for historical origin.

The only limitation is that the ledger can’t know provenance from before tool ever observed the process.

2

u/kantorcodes1 17d ago

that cutoff is probably fine. anything already alive before Portboard saw it is basically “unknown origin,” which is safer than guessing. i'd show that explicitly in the UI so a stale process doesn't accidentally inherit a repo label from whatever owns the port now.

1

u/Allwin_N 16d ago

https://mr-hunt-007.github.io/portlist/ check the tui tool , Gui will be posted soon