[Bug] Agents created outside the current app-managed store do not appear in the Agents tab

[jiyeonseo]

Summary

Agents created through the external buzz-acp CLI, or through a different Buzz app bundle/profile, do not appear in the desktop app's Agents tab.

This makes agents that are present and active on the local relay look as if they were missing.

Observed behavior

• The local relay contains the agent and the agent can participate in channels/respond through buzz-acp.
• The desktop app's Agents tab does not list that agent.
• The tab only shows agents registered in the current app's local managed-agent store.
• The production and development app bundles use separate managed-agent stores, so agents created in one are not automatically visible in the other.

Expected behavior

The Agents tab should either:

1. discover and display agents associated with the current community/relay, including externally managed buzz-acp agents, or
2. clearly distinguish app-managed agents from externally managed agents and provide an explicit import/adopt flow.

If adopting an existing agent is supported, it should preserve the agent's existing identity where possible rather than silently creating a duplicate.

Steps to reproduce

1. Start a local Buzz relay.
2. Create/configure an agent using the external buzz-acp CLI and connect it to the local relay.
3. Confirm that the agent is present in a channel and can respond to a message.
4. Open the Buzz desktop app connected to the same local relay/community.
5. Open the Agents tab.
6. Observe that the externally managed agent is not listed.

The same issue can be reproduced by creating an app-managed agent in a development build and then opening the production build.

Environment

• Buzz Desktop: 0.4.26
• Local self-hosted relay
• External agent runtime: buzz-acp
• macOS

Notes

The current behavior appears to come from the Agents view reading only the current app bundle's local managed-agent storage rather than merging relay-visible agents or offering an import path.

[davidglogan]

Confirming this from a real deployment tonight: stood up an agent (Grok Build, xAI) purely via the external buzz-acp CLI on its own dedicated VM — never touched via the Desktop app at all, by design (our project's security model deliberately keeps every agent's process off the machine running the human's own Desktop client).

The agent is fully functional at the relay level — correct role: "bot" channel membership, responds to @mentions, introduces itself in group channels, DMs work — but is entirely absent from Desktop's Agents tab, exactly as described here. Took a bit of investigation to confirm this was expected/by-design rather than a misconfiguration on our end (traced it to desktop/src-tauri/src/managed_agents/discovery.rs, which is scoped to locally-launchable runtimes only).

+1 on option 1 in the expected-behavior list (discover and display externally-managed buzz-acp agents associated with the current relay/community) — for architectures like ours where the agent intentionally never runs on the Desktop machine, there's currently no way to see it in the app at all, only via direct relay queries (buzz messages search --author <pubkey>, buzz channels members, etc.). A read-only "connected ACP clients" view would close that gap without requiring the adopt/import flow in option 2, which doesn't really fit this use case (there's nothing local to adopt — the agent's identity and process both live elsewhere by design).