Always-on service
On Linux, Briglia can run in the background as a systemd user service: it answers on Telegram with the terminal closed, starts at boot, and restarts itself after a crash. A Raspberry Pi 5 or a spare phone is a perfect home for it.
The service runs briglia daemon, which has no local chat — so Telegram must be configured first. On macOS there is no service installer yet: run briglia daemon in a terminal (or ask Briglia to set up a LaunchAgent for you).
Install
briglia service installThis writes ~/.config/systemd/user/briglia.service (Restart=always), enables and starts it, enables linger so it also starts at boot without a login (falls back to sudo loginctl enable-linger if needed), waits two seconds and reports the real state. The wizard offers the same thing as its last step.
Everyday commands
briglia service status | Is it running? (also the default for bare briglia service) |
systemctl --user stop briglia.service | Stop Briglia |
systemctl --user start briglia.service | Start it again |
journalctl --user -u briglia.service -f | Follow the log |
briglia service uninstall | Remove the service (Briglia and its data stay) |
One Briglia at a time: the terminal chat and the daemon share the same state and instance lock. To chat locally on a box that runs the service: stop the service, run briglia, then start the service again when you leave. Updates work from the service too — /upgrade from Telegram restarts it in place.
Keeping the machine awake
- Desktop Linux: the setup wizard's permissions step can disable automatic suspend (GNOME) or mask the systemd sleep targets.
- Headless boxes / Raspberry Pi: nothing to do.
- macOS: the system (not just the display) must stay awake — Energy settings, or
caffeinate -is briglia daemon.
Ubuntu Touch phones
A phone suspends completely when the screen turns off, freezing everything — including a Terminal session. That is why Briglia must run as a service there, and why it needs the keep-awake: a tiny system unit (briglia-keepawake.service) that holds a kernel wakelock. Installing it briefly remounts the system partition read-write, so it asks for the phone's passcode; briglia service install offers it (skip with --no-keepawake), and the companion app does it from its Always-on screen. Expect somewhat higher idle battery use — check the drain on the first day.
After an OTA update the keep-awake unit can vanish: briglia doctor and briglia service status both say so, and briglia service install puts it back.