feat(desktop): read-only shared fleet view for relay-hosted agents - #5412
Draft
bossriceshark wants to merge 1 commit into
Draft
feat(desktop): read-only shared fleet view for relay-hosted agents#5412bossriceshark wants to merge 1 commit into
bossriceshark wants to merge 1 commit into
Conversation
Add a Shared Fleet section to the Agents page that lists relay-hosted remote workers from current kind:10100 directory records, gated by an independent presence read so stale directory-only records never render as live. The surface is strictly read-only: no lifecycle, membership, or global-mention controls, and mention guidance stays channel-scoped. Add a strict kind:30178 shared team catalog reader (exact ['shared', 'true'] opt-in, single d-tag, schema versioning, replaceable-head semantics where a newer malformed/unshared head hides older shared heads, bounded paging with event-id dedupe) that projects only safe fields (name, member count). Resolve team card membership against local personas, the relay agent directory, and the owner-scoped shared catalog so relay-hosted members are reported as resolved-via-relay instead of falsely missing, while local deploy gating stays conservative. Scope relay-agent, presence, and catalog query cache keys by the active canonical relay URL (and account identity) so a community switch cannot briefly serve another tenant's records. Signed-off-by: Matt Rice <bossriceshark@users.noreply.github.com>
bossriceshark
marked this pull request as ready for review
August 9, 2026 17:03
bossriceshark
marked this pull request as draft
August 9, 2026 17:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a read-only Shared fleet section to the desktop Agents page and makes team cards relay-aware, so a Buzz Desktop acting as a controller against a self-hosted relay can see the agents that actually live there.
["shared","true"]opt-in, exactly onedtag, schema-versioned, replaceable-head semantics (a newer malformed/unshared head hides older shared heads rather than falling back), bounded paging with event-id dedupe. Only safe fields (display name, member count) are projected; prompts/provider config/paths are never exposed.Why
Self-hosted multi-device use case: agents run as
buzz-acpworkers on a home server, and other devices (Windows desktop, mobile) connect to the same relay as controllers. Today the Agents page renders only locally managed agents, so a healthy relay-registered fleet is invisible and teams referencing relay members are flagged as broken. This is the same ecosystem gap discussed around #4128 (remote/managed-agent visibility), but a separate, additive feature: inspection only, no remote lifecycle control.Testing
pnpm check(biome + file-size/px/pubkey guards) — cleanpnpm typecheck— cleanpnpm test— 4557 passpnpm build:e2e && playwright test tests/e2e/shared-fleet.spec.ts— 1 pass (bridge seeded with independent fixtures for directory, presence, and 30178 catalog; asserts a live worker renders with channels, a stale directory-only record does not, shared teams render with member counts, and the surface contains no action buttons)🤖 Generated with Claude Code
https://claude.ai/code/session_01HYzfZG6xwRGefUB9EAsh8q