From f9fe95d1820083764e33c8799c1d1af43365cc47 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Mon, 12 Jan 2026 01:32:54 +0000 Subject: [PATCH] docs: add central gateway workflow FAQ --- docs/start/faq.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/start/faq.md b/docs/start/faq.md index b7856367a..9ac28b171 100644 --- a/docs/start/faq.md +++ b/docs/start/faq.md @@ -283,6 +283,18 @@ The Gateway watches the config and supports hot‑reload: - `gateway.reload.mode: "hybrid"` (default): hot‑apply safe changes, restart for critical ones - `hot`, `restart`, `off` are also supported +### How do I run a central Gateway with specialized workers across devices? + +Yes. The common pattern is **one Gateway** (e.g. Raspberry Pi) plus **nodes** and **agents**: + +- **Gateway (central):** owns providers (Signal/WhatsApp), routing, and sessions. +- **Nodes (devices):** Macs/iOS/Android connect as peripherals and expose local tools (`system.run`, `canvas`, `camera`). +- **Agents (workers):** separate brains/workspaces for special roles (e.g. “Hetzner ops”, “Personal data”). +- **Sub‑agents:** spawn background work from a main agent when you want parallelism. +- **TUI:** connect to the Gateway and switch agents/sessions. + +Docs: [Nodes](/nodes), [Remote access](/gateway/remote), [Multi-Agent Routing](/concepts/multi-agent), [Sub-agents](/tools/subagents), [TUI](/tui). + ## Remote gateways + nodes ### How do commands propagate between Telegram, the gateway, and nodes?