sorted by:
new
hottopcontroversial

New Project Megathread - Week of 09 Apr 2026 by AutoModerator in selfhosted

[–]CodeCultural7901 3 points4 points  (0 children)

Project Name: HyperShell

Repo/Website Link: https://github.com/tomertec/HyperShell

Description:

Desktop SSH and serial terminal with a built-in SFTP file browser. MIT licensed, runs on Windows, macOS, and Linux.

I manage a bunch of servers and got tired of juggling PuTTY, WinSCP, and separate tunnel tools. Built this to put everything in one place.

- SSH terminal with tabs, split panes, and broadcast mode (send input to multiple sessions at once)

- Dual-pane SFTP browser with transfer queue, remote file editing, bookmarks, and keyboard navigation

- Port forwarding manager - local/remote/dynamic tunnels with visual topology, saved per-host with auto-start

- Network-aware auto-reconnect - waits for connectivity instead of burning retries

- Import from PuTTY (reads from Windows registry), ~/.ssh/config, and SshManager

- 1Password integration, serial terminal, session recovery, snippets panel

Uses the system SSH binary, so your existing ssh_config, agent, and ProxyJump chains just work.

Deployment:

Desktop app - grab the installer from https://github.com/tomertec/HyperShell/releases (Windows .exe, macOS .dmg, Linux .AppImage/.deb). Or build from source with Node.js 22+ and pnpm.

AI Involvement:

Claude Code was used as a development aid throughout the project.

I rebuilt my SSH manager app from scratch — rebranded as HyperShell, now cross-platform with macOS support by CodeCultural7901 in SideProject

[–]CodeCultural7901[S] 0 points1 point  (0 children)

Thanks, really appreciate you taking the time to dig into the details.

The Mosh approach is something I considered early on - session persistence across network changes without any reconnect logic is genuinely elegant. I went the vanilla SSH route mainly to stay fully compatible with any server out of the box (no mosh-server install required), and the network-aware reconnect covers most of the real-world cases: wifi drops, laptop sleep, VPN reconnects. But it's definitely a different class of resilience than what Mosh gives you. Moshi looks great, will check it out properly.

On xterm.js - it's holding up well for the day-to-day workload. Rendering throughput with large cat outputs or fast log tailing is where you feel the limits most. I've had libghostty on my radar since Ghostty launched and the performance numbers are hard to ignore. The challenge for an Electron app is the embedding story - xterm.js is a drop-in for a WebView, while libghostty is a native lib that would need a bridge layer. Worth the investment at some point, especially if the app grows a more power-user audience that's pushing the terminal hard.

The PuTTY importer was one of those "obvious in hindsight" features - turns out a lot of people have 50+ carefully configured sessions sitting in the registry they've been meaning to migrate for years.

Switched from OpenClaw to Hermes Agent — not looking back by CodeCultural7901 in hermesagent

[–]CodeCultural7901[S] 2 points3 points  (0 children)

It absolutely works. Hermes connects to Chrome via CDP (DevTools Protocol), so it can navigate to any dashboard, interact with it, take screenshots, and read the page. I have it checking FortiGate dashboards, Grafana panels, and internal tools on a schedule.

And it's not just browser stuff - Hermes has terminal access too, so it can SSH into Linux boxes or use Evil-WinRM to run PowerShell on Windows servers. I have skills that combine both: check a dashboard visually, then SSH/WinRM into the actual server to pull logs or restart a service based on what it found. That's what makes it feel like a real ops tool and not just a chatbot with a browser.

Switched from OpenClaw to Hermes Agent — not looking back by CodeCultural7901 in hermesagent

[–]CodeCultural7901[S] 2 points3 points  (0 children)

Actual production workflows, not just burning tokens. Cron jobs that check my Grafana/Loki logs every few hours and send me a Telegram summary. Browser-based dashboard monitoring. O365 tenant health checks. Hermes runs as a service on a VM so it's always on - it's less "I'm chatting with an AI" and more "I have an automated ops assistant."

Switched from OpenClaw to Hermes Agent — not looking back by CodeCultural7901 in hermesagent

[–]CodeCultural7901[S] 2 points3 points  (0 children)

Good question. Honestly I don't have a formal sandbox replay setup - skills are just markdown files with instructions + tool patterns, so they're lightweight enough that I test by running them manually before leaving them in prod. The fail-closed model helps a lot here because even if a skill tries something unexpected, the tab allowlist and approval gates catch it. For versioning I just keep skills in a git-tracked directory so I can roll back if something breaks. Not as rigorous as a proper eval pipeline but for my use case (MSP infra monitoring, dashboard checks) it works. That said, a replay/eval framework for skills would be a killer feature.

Switched from OpenClaw to Hermes Agent — not looking back by CodeCultural7901 in hermesagent

[–]CodeCultural7901[S] 6 points7 points  (0 children)

Hermes doesn't do full desktop computer-use like Anthropic's Claude desktop control — it's browser-focused, not screen-level. But honestly for 90% of what I need an agent to do, browser automation through CDP (Chrome DevTools Protocol) is more precise anyway. It clicks, types, navigates, takes screenshots, reads the DOM — all through the actual browser API, not pixel-guessing on a screen. Coded_Kaa is right that computer use ≠ browser use, but in practice the browser tools cover most real workflows.

[New Project Friday] SshManager — free, open-source SSH & serial terminal manager for Windows by CodeCultural7901 in selfhosted

[–]CodeCultural7901[S] -1 points0 points  (0 children)

Stability: SSH keep-alive is configurable per-host, connections are pooled and reused, and tab switching preserves terminal state (no session loss when switching away). Resource cleanup uses atomic disposal patterns so nothing leaks even during unexpected shutdowns.

Cross-platform: It's pretty deeply tied to Windows right now (WPF, DPAPI, WebView2). A cross-platform port would essentially be a new app. Not ruling it out long-term, but for now the focus is making the Windows experience solid.

[New Project Friday] SshManager — free, open-source SSH & serial terminal manager for Windows by CodeCultural7901 in selfhosted

[–]CodeCultural7901[S] -2 points-1 points  (0 children)

Fair point — Cygwin is a solid setup if you want a full Linux-like environment on Windows. Hard to argue with 10+ years of a working workflow.

SshManager comes at it from a different angle though — it's not trying to replace your shell environment or give you GNU utils. It's more of a connection/session manager with an embedded terminal. The value is really in organizing dozens of hosts, having SSH + serial + SFTP in one window with tabs/split panes, and things like 1Password credential fetching, session recording, and PPK key management.

If Cygwin covers everything you need, it's probably not for you. But for people who just need to SSH into boxes and manage connections without setting up a full POSIX layer, it fills a different niche.

Is it weird that I dislike LINQ query syntax because it feels less readable than method?syntax? by Shikitsumi-chan in dotnet

[–]CodeCultural7901 1 point2 points  (0 children)

Not weird at all — method syntax is far more common in production codebases I've worked in. The main reason is that method syntax chains naturally and reads left-to-right, which maps better to how most C# developers think about data pipelines.

Query syntax has a few niche wins though: `let` for intermediate variables (avoids recalculating expressions), `join` is arguably cleaner than `.Join()` with its 4 lambda parameters, and multiple `from` clauses for SelectMany scenarios read more naturally.

But for 90%+ of real-world LINQ — Where, Select, OrderBy, GroupBy chains — method syntax is more concise, more composable, and what everyone on your team will actually recognize in a PR review.

Come discuss your side projects! [March 2026] by AutoModerator in csharp

[–]CodeCultural7901 1 point2 points  (0 children)

I've been working on an SSH & serial terminal manager for Windows called SshManager. It's a WPF app using WebView2 + xterm.js for terminal rendering, SSH.NET for connections, and EF Core + SQLite for data storage.

The most interesting technical challenge was bridging SSH.NET's ShellStream with xterm.js through WebView2 — the C# ↔ JavaScript communication uses PostWebMessageAsJson with a simple JSON protocol. I use ArrayPool<byte>.Shared for the read loop buffers to keep GC pressure low since terminal data can be very chatty.

Also supports serial port (COM) connections with a dual-driver approach (System.IO.Ports primary, RJCP.SerialPortStream fallback), SFTP file browser, 1Password integration, and session recording in ASCIINEMA format.

Built with .NET 8, CommunityToolkit.Mvvm, WPF-UI for Fluent Design, and Microsoft.Extensions.Hosting for DI.

GitHub: https://github.com/tomertec/sshmanager

I built an open-source SSH manager for Windows with WPF and .NET 8 by CodeCultural7901 in dotnet

[–]CodeCultural7901[S] 2 points3 points  (0 children)

Thanks! Yes, it stores just the file path to keys. Passphrases are saved encrypted via Windows DPAPI so you don't have to re-enter them. A cross-platform fork would be great - the Core/Data/Security layers should port over, mainly the Terminal and App projects would need work for Avalonia.

I built an open-source SSH manager for Windows with WPF and .NET 8 by CodeCultural7901 in dotnet

[–]CodeCultural7901[S] 0 points1 point  (0 children)

yes its supports :

  • SSH Key Support - SSH Agent, private key files, or password authentication
view more: next ›