Unify TUI runtime commands with gateway and harden gateway restart

README.md

@@ -376,6 +376,8 @@ Runtime backend mode can be controlled live (persisted in `~/.local/share/flynn/
 
 This manual runtime mode control is the intended Pi activation/deactivation switch.
 
+In TUI sessions, `/runtime ...` is forwarded through the gateway/daemon command path (same control-plane behavior as Telegram/WebChat). `flynn tui` now auto-attaches to gateway and auto-starts local daemon+gateway if needed.
+
 To evaluate canary performance from audit logs, run:
 
 ```bash
@@ -652,6 +654,7 @@ pnpm tui:fs
 | `/model <tier>` | Switch active tier (`local`, `default`, `fast`, `complex`, or aliases `ollama`, `sonnet`, `haiku`, `opus`) |
 | `/model <tier> <provider/model>` | Hot-swap a tier's provider and model at runtime |
 | `/backend [provider]` | TUI-local command: show or switch local model backend (`ollama`, `llamacpp`) |
+| `/runtime <status\|activate pi\|deactivate pi\|use config>` | Forward runtime backend mode control to daemon/gateway command service |
 | `/login [provider]` | Authenticate with GitHub (OAuth device flow) |
 | `/reset` | Clear history |
 | `/status` | Show session info |
@@ -673,7 +676,7 @@ pnpm tui:fs
 
 TUI keyboard controls: `Esc` cancels active prompt/running response. `Ctrl+C` clears the current input; press `Ctrl+C` twice quickly to exit.
 
-Note: runtime backend mode control is a daemon/channel command (`/runtime ...`, `/backend ...` alias), not the TUI-local `/backend [provider]` switch.
+`flynn tui` now attaches to the gateway command path at startup (and auto-starts local daemon+gateway when unavailable), so `/runtime ...` in TUI matches Telegram/WebChat behavior. `/backend [provider]` remains the TUI-local backend switch for local tier providers.
 
 #### Runtime Model Switching
 
@@ -819,6 +822,9 @@ systemctl --user enable --now flynn
 
 # View logs
 journalctl --user -u flynn -f
+
+# From the repo root, rebuild + restart service after code changes
+make restart
 ```
 
 ## Hook Engine