Skip to content

Shared Dev Stack

Use this workflow when one machine hosts a team-accessible FlowLayer session for collaborative debugging.

  1. Host runs the server with explicit bind and token.
  2. Team members connect with the official TUI from their own terminals.
  3. Access is limited to trusted network paths (VPN or SSH tunnel).

Example server command:

Terminal window
flowlayer-server -c ./flowlayer.jsonc -s 127.0.0.1:6999 -token team-dev-token

Example client command:

Terminal window
flowlayer-client-tui -addr 127.0.0.1:6999 -token team-dev-token
  • decide ownership of start/stop actions before the session
  • treat stop-all as coordinated action
  • rotate session token when participants change
  • keep one shared config in version control
  • if clients fail auth (401/403), re-verify token distribution
  • if remote access is needed, use SSH forwarding instead of broad public exposure

See Remote Access and Session Token.