Run it
The gateway
The gateway is Brigade running as a WebSocket server with no terminal UI of its own — the long-lived process that channel adapters, cron jobs, and sub-agent spawns all need running. The TUI auto-starts one if needed; for an always-on crew you run it yourself.
Run it#
$ brigade gateway run --port 7777 --host 127.0.0.1 --verbose$ brigade gateway status$ brigade gateway stop$ brigade gateway restart| Flag | Default | Notes |
|---|---|---|
--port N | 7777 | Listen port (also BRIGADE_PORT) |
--host A | 127.0.0.1 | Bind address — loopback by design |
--verbose | off | Stream a one-line summary of every event |
--quiet | off | Suppress the live console stream |
--log-level X | info | trace / debug / info / warn / error / fatal |
Attach a TUI to a running gateway with brigade connect — same chat experience, but the agent runs in the gateway process, so you can disconnect and reconnect later while channels and cron keep running.
$ brigade connect --host 127.0.0.1 --port 7777Staying up#
The gateway writes a heartbeat file. An out-of-process supervisor watches it and respawns the gateway if its event loop wedges, rate-limited so a crash loop cannot flap:
$ brigade gateway superviseInstall as a service#
Bring the gateway up at login with a per-OS service installer — launchd on macOS, systemd on Linux, Task Scheduler on Windows:
$ brigade gateway install # register the service$ brigade gateway uninstall # remove itLoopback by default
127.0.0.1 on purpose. To reach it from another device, front it with something you trust (an SSH tunnel or a private network) rather than binding it to a public interface. Health-check a running gateway by pointing doctor at it with brigade doctor --host 127.0.0.1 --port 7777.