# LA Manager

A terminal interface for service notes, multi-hop SSH, and local HTTP entry points

Source: https://works.im0o.top/en/projects/la-manager/
Date: 2026-09-16
Tags: Developer tools, Go, SSH, TUI


With more machines, containers, and services, opening a page starts with several questions: which machine hosts it, which SSH hops are needed, and which local port points to it? The documentation and tunnel commands lived separately, so an infrequently used service meant another search through notes.

LA Manager puts the service catalog and connection controls in a Go terminal application. It starts with machine and service information; connections are explicit actions. Mouse and keyboard both work. Wide windows show a list beside details, while narrow windows switch between them.

![LA Manager TUI, redrawn with fictional nodes, services, and addresses](https://image.im0o.top/2026/20261117104258433.webp "LA Manager TUI, redrawn with fictional nodes, services, and addresses")

## Machines, SSH connections, and service entries

The interface shows SSH and service-entry states separately. A parent node may exist only as the route to a container: connecting it establishes that route, while service entries are opened individually when needed.

The configuration expresses dependencies with `via`. Connecting a child reuses the required parent connections, while details show SSH status and service-entry status separately. Disconnect confirmation explains the affected child nodes and services.

The catalog groups services under machines instead of presenting every URL as a separate card. After finding a machine, its details show the route and associated services, with actions for connection, browser access, interactive SSH, and VS Code Remote-SSH.

## Named entry points instead of remembered ports

A local reverse proxy routes by domain name. The browser gets a recognizable entry point while the application manages HTTP CONNECT and nested SSH behind it. Sites share a node's SSH connection but retain independent HTTP connection pools.

If the preferred local port is occupied, the application falls back to another port and displays the real address. Changing an entry point first establishes the replacement listener, then closes the old one after success.

Site configuration can reload as an atomic update. Invalid changes retain the existing configuration; unchanged sites keep their connections. Node and TLS changes require a restart and are distinguished from live-reloadable site changes.

## Recovering from a dropped connection

SSH keepalive detects connections that appear open but no longer respond. Unexpected disconnection triggers recovery only for nodes explicitly requested in this run or configured for automatic startup. Repeated failures increase the retry interval.

Recovery can be stopped manually. Disconnecting a parent closes dependent children, and exiting closes managed connections and listeners.

Tunnel recovery is separate from business-request retry. Reconnecting the network does not replay a failed HTTP request: a service may have been processing a submission, and reconnecting should not submit it again.

![Reconnect the tunnel without replaying a failed HTTP request](https://image.im0o.top/2026/20261117104252056.webp "Reconnect the tunnel without replaying a failed HTTP request")

## Local configuration

The catalog can be bundled with the program or supplied as an explicit file. Network configuration is separate. An automatic-start switch changes the next launch policy, and saving it edits only that field while preserving comments and unrelated settings.

SSH config import preview and local certificate management provide additional tools for existing connections and HTTPS entry points. They have explicit entry points rather than running during ordinary startup.

