About Farhelm

Farhelm

Farhelm is a browser-based control surface for persistent, tmux-backed development sessions. It is built for developers who run long-lived agents, shells, editors, and logs and need to reconnect from a laptop, phone, or tablet without restarting the work.

The app keeps the shell on your host and treats the browser as the viewer. A dropped network connection, closed laptop, or device switch should not kill the session you were waiting on.

What It Solves

Modern coding work often runs for longer than a single SSH connection. A Claude Code task may grind through a refactor, Codex may run tests in a separate worktree, and a Rails console or log stream may need to stay open while you step away.

Farhelm gives those processes a durable home:

• Persistent tmux sessions that continue after the browser disconnects
• A multi-session dashboard for projects and active terminals
• Browser and mobile access to scrollback and live terminal output
• State-aware indicators that show when an agent is working, waiting, ready, or exited
• Single-tenant operation on your host, with no shared filesystem

How It Works

Each terminal session starts inside tmux on the server. Rails streams the pane through ActionCable to xterm.js in the browser, captures scrollback for reconnects, and tracks session state from tmux, process data, and supported agent hooks.

You can close the tab, change devices, or move between networks. When you return, Farhelm reattaches to the same server-side session.

Who It Is For

Farhelm is for operators of parallel agentic coding workflows: solo developers, founders, and small engineering teams who want a private command center for many concurrent terminal sessions.

It is not a general shared terminal SaaS. It is designed around controlled access to your own host, your own projects, and your own tmux processes.

Contact

Questions, feedback, or support requests can be sent to support@h15n.com.