Skip to content

sshkeeper v0.8.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 04 Oct 19:16
· 10 commits to main since this release
v0.8.0
0cc2ef8

sshkeeper v0.8.0 — Session Workspace

v0.8.0 turns the main TUI into a live SSH workspace. Interactive SSH no longer
has to replace the sshkeeper interface: sessions live in embedded tabs and can
keep running while you return to the dashboard, manage tunnels, or open another
server.

Added

  • Embedded SSH tabs on every platform. Normal Connect opens a workspace tab.
    Unix uses a PTY; native Windows uses ConPTY. Terminal state is rendered by
    github.com/charmbracelet/x/vt, so full-screen terminal applications can keep
    running while another tab is active.
  • Workspace tab switching. Ctrl+PgUp / Ctrl+PgDn cycle tabs, Alt+0
    returns to Servers, Alt+1…Alt+9 select an SSH tab, and Alt+W closes the
    current SSH tab.
  • Selected-profile actions. On the wide dashboard press Tab to focus the
    right panel. It can Connect, Tunnel + Connect, start/stop a background tunnel,
    or open the full port-forward editor.
  • Tunnel + Connect. Enabled forwards start as an independent background
    ssh -N process, then sshkeeper opens an interactive SSH tab. The tunnel can
    be stopped later without closing the session.
  • Mouse input. Bubble Tea mouse events are enabled. The dashboard supports
    wheel navigation, server selection, clickable right-panel actions, and
    clickable workspace tabs.

Changed

  • Dead background tunnel records are garbage-collected from tunnels.json on
    load/reload, including their temporary SSH config files.
  • The Running tunnels manager reloads and shows live processes rather than
    retaining stopped entries from old sshkeeper runs.
  • Quitting with live embedded SSH tabs asks for confirmation.
  • The existing tmux backend remains available on Linux/macOS as an optional
    persistent backend for sessions that should survive the sshkeeper process.

Windows

The Session Workspace is native on Windows and uses the same ConPTY foundation
as password/key-passphrase authentication. The ConPTY child environment now
defines TERM=xterm-256color, so remote full-screen applications receive a
terminal type even when sshkeeper was launched from cmd.exe. No tmux, MSYS2,
or Cygwin layer is required.

Compatibility

No database migration is required. v0.8.0 includes the v0.7.6 quiet-sync
key-path repair, so Windows clients upgraded from older releases repair legacy
/home/.../.ssh/... identities even when the shared sync bundle itself has not
changed.

Assets 12
Loading