Outcome
Make Buzz Desktop's managed-agent runtime catalog extensible enough to install,
detect, authenticate, and run these self-hosted/local runtimes:
- Hermes Agent
- Kimi Coding
- OpenCode
- OpenClaw
Why
The current desktop UI already discovers, connects, and installs ACP runtimes,
but a self-hosted Buzz operator needs to use the model/runtime estate already
available on their machine or private network. These should be first-class
managed-agent choices, not manually edited commands with invisible failure
modes.
Scope
- Define one runtime-adapter contract: availability detection, install/update
strategy, ACP command/arguments, supported authentication methods, version
reporting, and actionable diagnostics.
- Add adapters for Hermes, Kimi Coding, OpenCode, and OpenClaw only where they
have a supported ACP-compatible launch path. Do not pretend a chat API is an
ACP runtime.
- Preserve the existing user-owned credentials model: Buzz must not ingest,
copy, or display provider tokens/subscription credentials.
- Surface availability, installed version, update availability, and failed
prerequisite in the existing runtime picker.
- Make an unavailable runtime non-selectable with a remediation action, rather
than silently falling back to a different provider.
Acceptance criteria
- Each adapter has deterministic detect/install/connect tests with fake
executables and no real provider credentials.
- A failed install, missing executable, incompatible version, or failed auth
produces a clear runtime-specific error.
- Runtime configuration is included in the managed-agent spawn hash, so a
change restarts stale ACP sessions safely.
- Documentation distinguishes local CLI/subscription auth from API-key auth.
- The four runtime integrations are independently shippable; unsupported ACP
capability is recorded explicitly rather than hidden behind a generic entry.
Non-goals
- Adding provider billing, key storage, model proxying, or remote code
execution beyond the permissions already granted to a managed agent.
Outcome
Make Buzz Desktop's managed-agent runtime catalog extensible enough to install,
detect, authenticate, and run these self-hosted/local runtimes:
Why
The current desktop UI already discovers, connects, and installs ACP runtimes,
but a self-hosted Buzz operator needs to use the model/runtime estate already
available on their machine or private network. These should be first-class
managed-agent choices, not manually edited commands with invisible failure
modes.
Scope
strategy, ACP command/arguments, supported authentication methods, version
reporting, and actionable diagnostics.
have a supported ACP-compatible launch path. Do not pretend a chat API is an
ACP runtime.
copy, or display provider tokens/subscription credentials.
prerequisite in the existing runtime picker.
than silently falling back to a different provider.
Acceptance criteria
executables and no real provider credentials.
produces a clear runtime-specific error.
change restarts stale ACP sessions safely.
capability is recorded explicitly rather than hidden behind a generic entry.
Non-goals
execution beyond the permissions already granted to a managed agent.