Replies: 4 comments 4 replies
|
good idea actually!! |
4 replies
|
Awesome! |
0 replies
|
a new feature coming in the next release is custom sidebar rows (5cfe5e5e). plugins and scripts can report custom metadata tokens, so users could theoretically extend each agent row to show related server details such as the tool and port. however, the panel is still specifically an agents panel. adding standalone server entries there would be semantically strange, especially for server panes that do not contain an agent. so this could cover showing server context alongside agents, but not the separate dev servers panel proposed here. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
When you have several panes open running different dev servers alongside agents, there's no quick way to see what's running where or jump to the right terminal. You end up either remembering which pane is which or clicking around to find the one with vite or postgres running.
requested change
A panel in the sidebar below the agents panel that shows detected dev servers: what tool, which port, which workspace. Clicking an entry focuses that terminal pane.
Detection would use argv inspection and screen output together so it catches most stacks without config: vite, next, nest, nuxt, astro, sveltekit, remix, django, flask, rails, spring, phoenix, and more. Port is correlated via /proc/net/tcp on Linux and screen URL patterns elsewhere. The panel would be opt-in under Settings > Experiments.
I have a draft implementation at hexxt-git/herdr if that's useful to look at.
why you want this
I use herdr across multiple work and personal projects at the same time, so there are usually 4-6 panes running servers across different workspaces. The port conflict situation comes up constantly: I try to start a server on 3000 and it immediately crashes because something else already grabbed it, then I have to go pane by pane to figure out what's holding that port. With a panel showing everything that's running and on which port, I'd know immediately what's conflicting without the hunt.
this is a gif of how my solution works:

vetting I already contributed to open source rust projects
https://github.com/crynta/terax-ai/graphs/contributors
All reactions