TUI

Documentation in progress

Some sections are still incomplete.

The same workspace, without the GUI:

thinkterm tui [DOMAIN ...]

This is a subcommand of the thinkterm binary rather than a second program, so it costs nothing while it is not running.

It is a peer, not a mirror

The TUI is not a read-only view of the GUI. It is another client of the same authoritative server, and it holds itself to the same rules:

• Space, Project and Thread data is accepted only from server snapshots
• every change waits for the server to acknowledge it before the display updates

So having the GUI and the TUI open at once cannot leave the two disagreeing about what exists.

It can do what the GUI can: new tabs, splits, resizing, closing panes, reordering the sidebar, and copy mode — with full mouse support.

Exiting does not end anything

Quitting the TUI detaches from the server. Every session inside it keeps running, exactly as when a GUI client disconnects.

That is what makes the obvious use case work: SSH into a machine, run thinkterm tui, do some work, disconnect. Or skip the GUI entirely on a machine where you never wanted one.

Options

Option	Effect
[DOMAIN ...]	Which mux client domains to show. Defaults to Local. Remote domains can also be attached later from the Connections panel
--prefer-mux	Connect to a background mux server rather than a running ThinkTerm GUI. The default prefers the GUI
--class <NAME>	The window class used to discover a running ThinkTerm GUI socket
--tui-config <PATH>	Use a different TUI settings file. The TUI's settings are independent of the GUI's

Related

• Remote — the servers the TUI attaches to
• Command Line — the rest of the thinkterm binary