Back to project index

Linux

GitHub Repository

Remote Terminal

A safer, repeatable way to reach and operate a home Linux machine from anywhere.

Context: Remote access automation and Linux operations

Period: 2026

Summary

Remote Terminal reaches a Linux host through a private Tailscale route. Its server mode records service and power state before changes, supports dry runs, reports health, and restores the previous configuration explicitly when remote operation ends.

From a remote device to a controlled Linux session

Remote device

A phone or computer initiates access

Tailscale

Private networking reaches the home machine

SSH

Authenticated access enters the Linux host

Safety layer

Checks and reversible changes protect operation

tmux

Persistent sessions survive reconnects

What the system handled

Designed Phone -> Tailscale -> Linux Host -> SSH -> tmux workflow.

Avoids exposing SSH directly to the public internet.

Adds reversible server-mode workflow and records current service state.

Includes dry-run support, AC-power checks, status scripts, terminal dashboard, whiptail menu, local Python web control panel, and Tailscale Serve helpers.

Technology

Stack

LinuxBashTailscaleSSHtmuxWireGuardsystemdOpenSSHPython HTTP serverJSON status reportingwhiptail

Areas

LinuxAutomationNetworkingSecurityOperationsHome Lab

Verified implementation

Remote access designed around reversibility

The engineering work centers on explicit state capture, dry-run behavior, a private route, and a dependable restoration path.

VPN

Private route

Tailscale keeps SSH reachable through the private network.

Dry run

Inspectable changes

Server-mode operations can be reviewed before service or power-policy changes.

State

Pre-change snapshot

SSH, tailscaled, power, and logind states are recorded before modification.

Restore

Explicit rollback

Exit scripts restore services and the previous lid/power policy.

Inspect the reversible server-mode scripts

Conclusions

  • Tailscale keeps SSH on a private route and preserves the familiar SSH and tmux workflow.
  • Dry runs, power checks, status output, and reversible service changes matter as much as connectivity because remote mistakes are harder to recover from physically.
  • The operational scope keeps sensitive actions explicit, inspectable, and under direct user control.

Want to inspect the implementation?

The repository contains the source, setup notes, and development history.

Open repository