flowlayer-client-tui
// CLI / flowlayer-client-tuiv1.1.1
flowlayer-client-tui is the official terminal client for a running server session.
flowlayer-client-tuiflowlayer-client-tui -addr <host:port>flowlayer-client-tui -addr <host:port> -token <value>flowlayer-client-tui -config <path>Options
Section titled “Options”| Flag | Meaning |
|---|---|
-addr <host:port> | Server address |
-token <value> | Bearer token |
-config <path> | Read session.addr and session.token from config |
-h, --help | Print help |
--version | Print version |
-v is not supported.
Resolution behavior
Section titled “Resolution behavior”Default runtime options without flags:
addr:127.0.0.1:6999token: empty
If -config is provided:
- read
session.addrwhen present - read
session.tokenwhen present
If CLI flags are explicitly provided, they override config values.
Resolved address must be a valid host:port.
Common invocations
Section titled “Common invocations”flowlayer-client-tui -addr 127.0.0.1:6999 -token dev-tokenflowlayer-client-tui -config ./flowlayer.tui.jsoncExit code semantics
Section titled “Exit code semantics”0: success, help, or version2: CLI usage/config resolution error1: runtime launcher error
Argument parsing rules
Section titled “Argument parsing rules”- positional arguments are rejected
- unknown flags are rejected with usage help
- config parsing is strict and fails on unsupported fields
-configcan be combined with-addror-token; CLI flags win
Connection lifecycle
Section titled “Connection lifecycle”- Resolve
addrandtokenfrom flags or config. - Open a WebSocket to
<addr>/wswithAuthorization: Bearer <token>. - Receive the initial snapshot, then live events until disconnect.
- On
Ctrl-Cor fatal protocol error, the TUI exits with the matching code.
Related docs: Client / TUI, Server and TUI Modes, Session Token, Download.