Skip to content

[FEATURE] Unified Multi-Host Tmux Monitor #1360

Description

@deanxbox

Title

Desktop (Windows, Linux, macOS) and Web App

Platform

Desktop App - Windows

Is it related to an issue?

Currently, Termix's Tmux Monitor only displays sessions belonging to one SSH host at a time, even when Tmux Monitor is enabled across multiple hosts.

For users managing several remote Linux servers, this creates unnecessary friction. Switching between tmux sessions on different hosts requires returning to the Host Manager and reopening Tmux Monitor for the desired host.

For example, I manage four VPSs running Minecraft servers and a Discord bot. Each VPS has its own persistent tmux sessions. I would like to monitor and switch between all these sessions from a single interface.

The current limitations are:

  • No unified overview of tmux sessions across multiple hosts.
  • No direct switching between sessions belonging to different hosts within Tmux Monitor.
  • No consolidated view of session activity and resource usage across servers.
  • Additional navigation is required whenever switching between hosts.

A unified, multi-host Tmux Monitor would solve these problems by providing one central location for monitoring and managing all existing tmux sessions, regardless of which SSH host they belong to.

This would be especially useful for developers, system administrators and anyone managing multiple applications across remote servers, without requiring Auto Tmux or additional software on the remote machines.

The Solution

Extend the existing Tmux Monitor to support monitoring and managing tmux sessions across multiple SSH hosts simultaneously, rather than displaying sessions from only one selected host.

The interface should provide:

  1. Unified session tree: Display all hosts with Tmux Monitor enabled in a single expandable tree, with their respective sessions, windows and panes underneath.

  2. One-click switching: Clicking a session or pane on any host should immediately display its live terminal preview, without needing to navigate back to the Host Manager.

  3. Multi-host monitoring: Display session activity, CPU usage and other existing tmux metrics across all connected hosts.

  4. Session management: Preserve the existing functionality for attaching, creating, renaming and managing sessions, regardless of which host they belong to.

  5. Host filtering: Allow users to display all hosts or filter the monitor to specific hosts.

  6. Persistent layout: Remember expanded hosts, selected sessions and the last active pane between visits.

The existing single-host monitoring functionality should remain available for users who prefer it.

Ideally, the unified monitor would work using existing SSH connections and require no additional software on the remote hosts.

Additional Context

I'm currently using Termix Desktop 2.8.0 to manage multiple remote Linux servers, including Minecraft servers and a Discord bot.

Each server has its own tmux sessions, and I have Tmux Monitor enabled on every host.

Currently, opening Tmux Monitor through a host's action button displays only that host's sessions. To inspect another server, I must return to the Host Manager and open the monitor for that host.

I'd love to have a single Tmux Monitor that works similarly to an infrastructure dashboard:

Server A
└── minecraft
└── Window 0

Server B
└── minecraft
└── Window 0

Server C
└── minecraft
└── Window 0

Server D
└── riyad-bot
└── Window 0

This would make it significantly easier to manage multiple applications running in persistent tmux sessions.

I deliberately keep Auto Tmux disabled because I prefer opening normal SSH terminals without being prompted to create or attach to sessions.

A unified monitor would let me access all my existing sessions directly without changing that preference.

The current Tmux Monitor already has much of the functionality needed. The primary improvement would be extending its navigation and monitoring capabilities to multiple hosts within the same interface.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions