Skip to content

docs(deploy): always-on agents for any client (thin UI + server backend) - #3551

Open
PabloTheThinker wants to merge 2 commits into
block:mainfrom
PabloTheThinker:docs/self-host-always-on-agents
Open

docs(deploy): always-on agents for any client (thin UI + server backend)#3551
PabloTheThinker wants to merge 2 commits into
block:mainfrom
PabloTheThinker:docs/self-host-always-on-agents

Conversation

@PabloTheThinker

@PabloTheThinker PabloTheThinker commented Jul 29, 2026

Copy link
Copy Markdown

Summary

Documents and packages the self-host layout many operators already run:

  • Any client: Buzz Desktop (macOS/Windows/Linux), web, mobile, or buzz CLI
  • Backend: buzz-relay + always-on buzz-acp (systemd) on a machine that stays up

Not laptop-specific — laptops are only one example of a thin client. Agents must not die when a single device sleeps.

Changes

  1. docs/self-host-always-on-agents.md — guide for everyone:
    • architecture (multi-client → one backend)
    • host string = community footgun
    • relay + systemd + Desktop / web / mobile / CLI
    • smoke test + troubleshooting
  2. deploy/systemd/buzz-acp@.service + env example
  3. Cross-links from buzz-acp and compose READMEs

Test plan

  • Dogfooded self-hosted relay + multi-agent buzz-acp fleet
  • Mention smoke: agent reply from server harness
  • Wording review: any client, not laptop-only
  • Maintainer: optional enable unit from template on a test host

Related

  • Closed-relay join UX still separate
  • No relay protocol changes

DCO signed.

Document the production layout where Buzz Desktop runs on a laptop and
buzz-acp agents stay on a server (same idea as a remote Hermes backend).

Add systemd template units under deploy/systemd and cross-link from
buzz-acp README. Emphasize host-string community selection so self-hosters
do not join an empty workspace via localhost vs public hostname mismatch.

Signed-off-by: Pablo Navarro <thethinker.pablo@protonmail.com>
@PabloTheThinker
PabloTheThinker requested a review from a team as a code owner July 29, 2026 14:40
Clarify that Desktop/web/mobile/CLI are interchangeable thin clients and
that the backend (relay + buzz-acp) is for every operator/team, not a
laptop-specific setup.

Signed-off-by: Pablo Navarro <thethinker.pablo@protonmail.com>
@PabloTheThinker PabloTheThinker changed the title docs(deploy): always-on agents with Desktop as thin client docs(deploy): always-on agents for any client (thin UI + server backend) Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant