Local & serial

Beyond remote SSH, the Desktop build runs two kinds of local sessions in the very same terminal: a local shell and a serial/UART port. Both are tabs like any SSH session — rename them, detach them into their own window, theme them per usual.

Local terminal

A real local shell, backed by a native PTY (pty4j). Pick Local terminal from the sidebar's Local group or the + launcher.

Serial / UART

Talk to a device over RS-232 / USB-serial (a router console, a microcontroller, a Pi header). Backed by jSerialComm.

Connect

  1. Sidebar Local group (or +) → Serial.
  2. Pick the port from the dropdown. The refresh button beside it re-scans attached ports.
  3. Set baud rate, data bits, parity, stop bits and flow control — or load a saved profile.
  4. Connect. The session opens as a terminal tab.

Profiles

Common device settings can be saved as named profiles (e.g. Cisco console 9600 8N1) and reused. Serial settings carry no secrets, so they live in the normal settings file — not the secure store.

Reconnect reopens the same port, so after you replug a cable or reboot the device, one click brings the console back without retyping baud/parity. There is no terminal-resize signal on a serial line, and reads stream as they arrive (like minicom), not in fixed blocks.

Serial and local-PTY sessions are Desktop-only — the seam returns nothing on Android and iOS, so these entries don't appear there.

Previous
File manager
Next
Desktop CLI