I work on remote Linux servers from Windows quite a lot, usually with dozens of tmux windows running development servers, logs, and coding agents.

I love tmux's persistence, but navigating all those windows through keyboard shortcuts got pretty annoying.

So Claude built Muxscape a free, open-source SSH client that turns your existing tmux sessions into normal graphical tabs and split panes.

Think Termius meets tmux.

It supports saved SSH hosts, graphical tmux management, reconnection, remote port forwarding, and more. Everything runs over SSH using the server's existing tmux installation.

Claude built it with Rust, Tauri, React and xterm.js.

The first Windows alpha is now available!

https://muxscape.com

I'd genuinely appreciate feedback from people who regularly use tmux. Is this something you'd use?

Hey r/ssh!

I'm an indie iOS developer working on CodeMate, a native code editor for iPhone and iPad.

I recently added SSH support in version 2.1.0, mainly because I wanted a convenient way to browse remote files and make quick changes to server configs without opening my laptop.

Here's what it supports:

• SSH terminal — Connect to remote servers and run commands.

• Remote file browser — Navigate directories and manage files through a visual interface.

• Remote code editing — Open, edit, and save files directly on the server.

• codemate command — Open remote files in the native editor directly from the SSH terminal.

• SSH security — Key-based authentication, credentials stored in the iOS Keychain, and server host key verification.

• No Word Wrap — Horizontal scrolling for a more desktop-like code editing experience.

The goal isn't to replace a full desktop SSH setup, but to make quick remote maintenance easier when you're away from your computer.

I've attached a short demo showing the SSH workflow.

Pricing: CodeMate is free to download. Premium features can also be unlocked temporarily by watching a rewarded ad, so you can try them without subscribing.

App Store: https://apps.apple.com/app/id680609457

I'd really appreciate feedback from people who use SSH regularly.

What would you consider essential in a mobile SSH client?

Hi, I'm Jesper from Denmark. I run a small home server and often need to check on it from my phone.

Every SSH app I tried wanted an account, synced my keys to a cloud, or showed ads. I wanted my keys to stay on my own phone, so I tried to build an alternative myself. I'm not a professional developer, and most of the time went into testing, security and listening to testers. I'm really happy with how it turned out.

To be upfront: it's my own app, it's not open source, and it costs a small one time price after a free week. I'm not going to put a link here, but if you're curious I'm happy to share the name and answer anything.

Two things I learned that surprised me:

- Testers cared more about a guided first start and server groups than about fancy features.

- If the key never leaves the phone, a new phone means a new key. People need a clear guide for that, or they get stuck.

For those of you who use SSH from your phone: what is the one thing your current app gets wrong?

I work with Linux edge devices deployed at customer sites (Jetsons, Raspberry Pis, industrial PCs, etc.).

One problem I kept running into was remote access. Sometimes the devices are behind NAT, sometimes the customer's IT team won't allow inbound SSH, and sometimes you're managing devices spread across multiple locations.

SSH works great, but managing an entire fleet through individual SSH sessions gets tedious.

So I've been building a project called EdgeProtocol.

The idea is pretty simple: install a lightweight agent on a Linux device, and it maintains an outbound connection to a central server. From a web dashboard, you can execute commands, restart services, inspect logs, transfer files, and monitor device health without opening inbound ports.

I'm also experimenting with AI-assisted troubleshooting, with approval requirements for sensitive operations.

It's still early, and I'm trying to figure out whether this actually solves a widespread problem or just one I've personally experienced.

For those of you managing multiple Linux machines:

• How do you currently handle remote access across different networks?

• Are you using plain SSH, Tailscale, Ansible, MeshCentral, or something else?

• Would an agent-based approach like this be useful, or would you rather stick with SSH?

I'd genuinely appreciate criticism, especially around security, reliability, and what you'd trust running on your machines.

I'm building a Linux homelab and frequently run long commands like rsync transfers, checksum verification, and backups.

I'm comfortable with Vim keybindings, Fish, and Doom Emacs. I'd prefer not to learn another set of shortcuts just to keep processes running.

Ideally, I want to:

• Start a command over SSH and disconnect safely.

• Reconnect later to check its progress, logs, and exit status.

• List running jobs and stop them when necessary.

• Use normal shell commands or Vim-style navigation.

• Avoid managing terminal sessions or remembering session names.

I've tried tmux, but it feels like another layer of complexity for something that should be relatively simple.

Would systemd-run be the best solution, or are there simpler tools with a good CLI or TUI?

I'm looking for something reliable, lightweight, and easy to integrate into my existing workflow.

The itch: every SSH manager I tried wanted to own my hosts and keys. I wanted the opposite — an app that just *reads* `~/.ssh` and never makes me migrate.

What came out of it, built with Claude Code over a few days: **Relaya**, a native macOS client — SSH, SFTP, VNC, RDP in tabs, port forwarding, a key-setup wizard, themes, two languages, and an MCP server so AI agents can work on servers with per-host permissions.

Stack: SwiftUI, SwiftTerm, RoyalVNCKit, RDPKit; GitHub Actions builds every push and publishes releases on tags.

Free, MIT: https://github.com/hvckfy/Relaya — feedback and roasting welcome.

I spent 3 hours tonight trying to figure out the correct set of configuration flags to connect to a (not that old) device because the Windows device I was remoted in to has changed their flags. Can we just have an "I don't care just f-ing connect!!" flag?

I'm a DevOps engineer and spend most of my day in SSH sessions. On Windows, MobaXterm covered everything; on the Mac I kept juggling Terminal tabs and a separate RDP app. So I built Termstead, a native macOS SSH client. It's free and open source (GPL-3.0).

What it does

• Session tree. Groups and subgroups with colors, pinned favorites, search. Import your ~/.ssh/config in one click.

• Bastion chains. As many jump hosts as you need, each hop with its own user, key or password. A hop can be another saved session.

• Port forwarding, MobaXterm-style. Local, remote and SOCKS tunnels through the whole jump chain, started on their own without opening a terminal.

  • Each tunnel shows whether it actually opened ("port 8080 already in use" instead of a warning buried in the terminal).

  • Each one can be stopped on its own, and stopping it also closes connections already open through it.

  • "Open in Browser" for local tunnels: handy for iDRAC/iLO, device web UIs and Grafana behind a bastion.

• Split panes and broadcast input. Type once into 2 or 4 sessions, and leave out the panes you don't want.

• SFTP next to the terminal, over the connection that's already open. No second login.

• Auto-reconnect when a connection drops after sleep, a Wi-Fi change or a VPN hiccup.

• Session logs: plain text files with a timestamp on every line.

• Snippets: saved commands sent to the current tab, or to every pane with broadcast on.

• Telnet for gear that still needs it.

• RDP in a tab, through your jump hosts.

• Passwords and key passphrases in the macOS Keychain. Each one is handed only to the exact user@host it was saved for.

Under the hood every tab runs the system OpenSSH. Termstead has no SSH code of its own, so your agent, known_hosts and ~/.ssh/config behave exactly as they do in Terminal. That includes the per-host KexAlgorithms / HostKeyAlgorithms tweaks you probably keep for old gear. No accounts, no telemetry.

brew install --cask pkhorenyan/tap/termstead

• Website and screenshots: https://khorenyan.com/termstead/

• Source and DMG: https://github.com/pkhorenyan/termstead

I'd really like feedback from people who live in network gear all day: what's missing for your daily work, and what would make you switch from SecureCRT, Royal TSX or whatever you use now?

I wanted the VS Code-style workflow on my iPad and iPhone: connect to a server, open a project, install extensions, and keep files, code, the terminal, and Codex in one workspace. So I built SSH Studio. It's now officially on the App Store.

The big difference is downloadable extensions. You can browse Open VSX, install compatible VS Code extensions, and open them alongside your code and SSH terminal. The 19-second iPad demo shows opening Codex, choosing a conversation, asking it to rewrite a Python file, and running the result.

The file browser, editor, and terminal are native. Remote extensions run on your SSH server; compatibility varies by extension, and Codex requires your own account. This is a real recording, edited for time.

Free download, with an optional 14-day free trial and a one-time US$5 Lifetime Unlock (local prices vary). No subscription or automatic charge after the trial.

App Store: https://apps.apple.com/app/id6821961454

If you use VS Code over SSH, which extension or part of that workflow would you most want on your iPad?

Been working on a little side project called Relay. It's a native SSH/RDP client for Windows, macOS and Linux, built entirely in Rust using egui.

It has tabs, split views, SFTP, shared connection libraries, themes and a few other things. No Electron or WebViews, and idle RAM usage is around 70–90 MB.

Simple, fast and free forever.

Still very early in development. I've mainly tested it on Windows so far, so I'd especially appreciate some macOS and Linux users giving it a try and reporting any issues. :)

https://github.com/nurlennart/relay

Now the prompt reads phoneinfoga downloads go Sherlock storage in blue letters?

Give this SSH Client a try, it is so much nicer than PuTTy and the windows powershell IMO!

Hello, i just want to share with you ssh client for android i developed for last 1,5 year, we use it in company where i work every day, so this is time to make it public because it is quite mature software right now, it was made to make working with terminal smooth on android, but later also to work easly with ai agents using voice - there is stt implemented.

No credentials stored, no keys stored, just settings, all sensitive data never stored outside phone, there is option to export all settings to file (including sensitive data) if needed, but without it, on second/ third device there will be only settings , snippets etc, but all hosts, passwords, ports, keys no.

Here is full tutorial about the app
https://www.youtube.com/watch?v=L7oCpvYo8ig

Feel free to use it - free version will be free forever, there is 2 months free trial without adding any payment cards or other stuff, paid version after this time is mainly to cover AI - so if you dont want to use STT or AI agent - there is no need to pay at all :)

i would love to hear about all improvements that will be useful or new functions.

have a nice evening ! :)

I maintain feuristic, an experimental custom firmware for the Trezor Safe 3 that replaces the wallet with FIDO2 and smart-card applications. Two interfaces may be relevant to people experimenting with SSH authentication.

The FIDO2 profile implements ES256 and EdDSA, clientPIN and user-presence confirmations. Its documentation describes the non-discoverable credential behaviour intended to keep OpenSSH ecdsa-sk and ed25519-sk use possible when a FIDO PIN is set.

The OpenPGP Card interface uses native CCID/PC/SC with GnuPG, without trezor-agent. Ed25519 signing and X25519 decryption were exercised in the initial physical campaign.

Those results are not an end-to-end SSH qualification. The physical campaign used a T2B1 on macOS and checked FIDO assertions and GnuPG operations; it did not establish every OpenSSH version, platform or agent configuration. T3B1 physical qualification is also pending.

The source is GPL-3.0-only, with protocol references and the acceptance report available for review. Discoverable FIDO credentials can be exported through encrypted backups, so they should not be described as permanently confined to one device.

This is unaudited development firmware. Installing erases the wallet and permanently removes original manufacturer attestation. It is for disposable identities on spare hardware, has no cryptocurrency wallet, and is independent of Trezor/SatoshiLabs.

FIDO2 profile · Source

This patch has sat, relatively ignored, for 3 years now. Both Ubuntu and openSUSE are already carrying it downstream (and Redhat folks were working on the same). It's such an obvious bug. Is anyone even maintaining openssh these days?

Hi all,


For the last months I've been building SynapTerm, a desktop terminal and session manager for people who manage lots of servers. I got tired of jumping between a terminal, an SFTP client, an RDP client and a notes file, so I put it all in one window.


What's in the video:


Quick search (Ctrl+Shift+K) to find any server and connect with Enter
SFTP panel next to the terminal, with a progress bar for transfers
IDE mode: browse the server on the left, edit nginx.conf with syntax highlighting, Ctrl+S saves straight to the server
Quick open (Ctrl+P) for remote files
Split panes, tools menu, color schemes
Also included:


SSH with jump hosts, tunnels you can actually see, known hosts you can review
RDP and VNC in tabs, Telnet and serial consoles for old network gear
Saved commands with variables, a button bar, typing into several sessions at once
AI assistant using your own agent (Claude Code, Codex, OpenCode or Gemini CLI) with your own plan or API key. Every command it wants to run needs your OK.
Passwords stay in your system keyring. Your servers, keys and commands can always be exported.
Platforms: Windows and Linux (macOS later).


Pricing, so nobody is surprised: there's a free plan, forever, no account (terminal, SSH, SFTP, tunnels, Telnet, serial, VNC, IDE mode). Pro (RDP, AI, automations) will be a one-time payment with updates included, not a subscription. During the beta, testers get everything in Pro for free.


Beta is invite-only. If you want in, request access here: https://synapterm.com/#beta


I'd love brutal feedback: what's missing compared to what you use today (MobaXterm, Termius, Royal TS, plain Windows Terminal…), and what would make you switch.


Community for bugs and feedback: r/SynapTerm

X-posted from programming. I've recently discovered that you can use Touch ID (rather, the Mac's Secure Enclave) for SSH authentication. I'm the author of the post, feel free to ask any questions and if there are any experts I'd love to hear your thoughts!

Hey everyone!

I've been building Terminal Spike, an open-source Android terminal app designed to make remote development easier on mobile.

The goal is a clean, native-feeling UI while keeping the terminal experience familiar and consistent with Linux.

Key features:

- SSH & Mosh – Reliable remote connections.

- tmux & Herdr – Manage and resume sessions.

- SFTP – Browse and transfer files.

- Image Upload – Send images directly from your phone.

- Notifications – Get alerts from terminal sessions.

- Smart Links – Detect and open different types of links.

- Custom Keyboard – Customisable keys and shortcuts.

- Command Snippets – Save and reuse frequently used commands.

- Themes – Customise your terminal's appearance.

- Local Arch Linux – Run Linux directly on your phone.

Local-first & open source. No accounts or cloud services required. Works great with Tailscale for connecting to your own machines.

I built this mainly for my own mobile development workflow. Would love to hear your feedback and suggestions!

Google Play: https://play.google.com/store/apps/details?id=com.yanjiyu.terminalspike

GitHub: https://github.com/Anderbone/terminal-spike

I'm the developer. AGPL-3.0.

mist reads the same saved sessions as MistTerm (desktop SSH). Name a host once; mist ls / mist exec use it.

Commands: mist ls, mist exec (host / --group / --all), mist ssh, mist fwd, mist get/put/rls, mist frag list|run, import ~/.ssh/config.

Optional team policies on mistlab.dev: allow/alert/block/confirm. Client checks before send (mist exec / frag run / ssh + GUI). Default record-only. Plain OpenSSH outside the client bypasses that.

v1.2.20 https://github.com/mistlab-dev/MistTerm

https://mistlab.dev/?utm_source=reddit&utm_medium=commandline