You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support for terminal multiplexers other than tmux (e.g. Herdr)?
#4943
Hi! I'm running Gas Town for a small Go project and I really like the polecat and refinery workflow. I do all my work in Herdr (https://herdr.dev), a terminal workspace manager built for coding agents. Gas Town agents run in their own tmux sockets, so right now I attach to them read-only from Herdr panes to follow what they're doing. That works, but agents started by Gas Town aren't first-class in Herdr: there's no lifecycle state, no agent read/prompt, no notifications.
Looking at the code, internal/tmux is used directly in many places (sessions, send-keys, capture-pane, env propagation), and I couldn't find a backend abstraction.
Would you be open to a small interface for the session/multiplexer layer, with tmux as the default implementation? Herdr has a socket API (create panes, start agents, read output, send input, wait for states) that could implement it. I'd be happy to help, but wanted to ask first whether this fits the direction of the project before anyone writes code.
Related: #295 asks for zellij, and #3538 shows the Windows effort hitting the same hard tmux dependency. A small backend interface could help all of these cases, not just Herdr.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi! I'm running Gas Town for a small Go project and I really like the polecat and refinery workflow. I do all my work in Herdr (https://herdr.dev), a terminal workspace manager built for coding agents. Gas Town agents run in their own tmux sockets, so right now I attach to them read-only from Herdr panes to follow what they're doing. That works, but agents started by Gas Town aren't first-class in Herdr: there's no lifecycle state, no
agent read/prompt, no notifications.Looking at the code,
internal/tmuxis used directly in many places (sessions, send-keys, capture-pane, env propagation), and I couldn't find a backend abstraction.Would you be open to a small interface for the session/multiplexer layer, with tmux as the default implementation? Herdr has a socket API (create panes, start agents, read output, send input, wait for states) that could implement it. I'd be happy to help, but wanted to ask first whether this fits the direction of the project before anyone writes code.
Related: #295 asks for zellij, and #3538 shows the Windows effort hitting the same hard tmux dependency. A small backend interface could help all of these cases, not just Herdr.
All reactions