gormes gateway
gormes gateway
Section titled “gormes gateway”Runs every configured channel through one gateway.Manager that drives the
same kernel + tool loop as the TUI.
gormes gateway status and gormes whatsapp are runtime-ready and
row-backed: they accept invocation even when the underlying live service is
not running, and respond with deterministic structured output instead of an
unknown-command failure.
Synopsis
Section titled “Synopsis”gormes gateway [flags]gormes gateway [command]Subcommands
Section titled “Subcommands”| Command | Purpose |
|---|---|
gormes gateway discover | Discover local Gormes gateways via Bonjour/mDNS |
gormes gateway install | Manage gateway install through the platform service helper |
gormes gateway probe | Probe gateway reachability, discovery, health, and runtime status |
gormes gateway reload | Reload live Gormes gateway config without restarting |
gormes gateway restart | Restart through the service manager or the validated runtime record |
gormes gateway start | Manage gateway start through the platform service helper |
gormes gateway status | Inspect configured gateway channels and persisted runtime state |
gormes gateway stop | Stop the live Gormes gateway recorded in runtime status |
gormes gateway uninstall | Manage gateway uninstall through the platform service helper |
gormes gateway usage-cost | Summarize token usage costs from gateway session metadata |
| Flag | Default | Purpose |
|---|---|---|
-h, --help | help for gateway |
Lifecycle Behavior
Section titled “Lifecycle Behavior”gormes gateway restart first asks the platform service manager to restart
the gateway when one is available. If that path is unavailable, it falls back
to Gormes’ validated runtime record: a live managed gateway is interrupted,
waited on, and relaunched; a missing or stale runtime record starts a fresh
gateway instead of failing with “nothing to restart.” PID-reuse or permission
validation failures are not killed.