This seems like a complex solution to a simple problem. In sshd_config there are some directives that can close unused connections. [1][2] as of OpenSSH 9.2
Another solution is to set a read-only shell timeout on servers and managed clients. This can annoy people causing them to do silly work-arounds so coordinate with your teams before applying this everywhere. Find an agreed upon and reasonable timeout that does not conflict with audit requirements that vary by company.
For clarity, it is a mess of a solution, and the key features I wanted was to have a good overview of a variety of ssh sessions I was having open as I realized I was giving prompts to the wrong claude session hence I have have a name for every agent that isn't changing and also a sense if it is active or not. Basically, i wanted a dashboard for ssh.
What I didn't realize that claude could build me my own little ecosystem. Every single thing here is vibe coded. The java terminal, however, kind of sucks. But, it solves my problem as my needs changed.
If I was one of the cool kids, then I'd probably use Zellij and have that worker peon notification system set up... BUT, I'm happy to live in my own little bubble since I'm not (nor have I even been) a cool kid.
I think if you are doing it as a learning exercise that is great. It is unfortunate that AI did not give the simple solutions.
For what it's worth many of the "cool kids" I went to school with ended up failing at life so its probably not something one should aspire to. Your path of enlightenment is far more valuable. There's just something wrong with the thinking machines.
This seems like a complex solution to a simple problem. In sshd_config there are some directives that can close unused connections. [1][2] as of OpenSSH 9.2
Another solution is to set a read-only shell timeout on servers and managed clients. This can annoy people causing them to do silly work-arounds so coordinate with your teams before applying this everywhere. Find an agreed upon and reasonable timeout that does not conflict with audit requirements that vary by company.
[1] - https://man.openbsd.org/sshd_config#ChannelTimeout[2] - https://man.openbsd.org/sshd_config#UnusedConnectionTimeout
For clarity, it is a mess of a solution, and the key features I wanted was to have a good overview of a variety of ssh sessions I was having open as I realized I was giving prompts to the wrong claude session hence I have have a name for every agent that isn't changing and also a sense if it is active or not. Basically, i wanted a dashboard for ssh.
What I didn't realize that claude could build me my own little ecosystem. Every single thing here is vibe coded. The java terminal, however, kind of sucks. But, it solves my problem as my needs changed.
If I was one of the cool kids, then I'd probably use Zellij and have that worker peon notification system set up... BUT, I'm happy to live in my own little bubble since I'm not (nor have I even been) a cool kid.
I think if you are doing it as a learning exercise that is great. It is unfortunate that AI did not give the simple solutions.
For what it's worth many of the "cool kids" I went to school with ended up failing at life so its probably not something one should aspire to. Your path of enlightenment is far more valuable. There's just something wrong with the thinking machines.
It seems like the Github ReadMe lacks the "Getting Started" section. I don't understand how to install/use this.
Thanks, I had claude update it.