OpenClaw ACP agent can’t publish replies
- Dominant language
- Rust
- Stars
- 32.7k
- Forks
- 4.3k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 253
Description
I’m using Buzz Desktop with a local OpenClaw agent over the OpenClaw ACP bridge. The agent receives messages and generates a response, but the harness instructs it to publish via buzz messages send, which fails because BUZZ_PRIVATE_KEY is not set. I don’t want to expose or paste the private key into OpenClaw. Is OpenClaw Gateway-backed ACP supported for managed agents? If so, what’s the recommended secure configuration?
Contributor guide
Research direction
Start by reproducing the Buzz Desktop flow with a local OpenClaw agent over the OpenClaw ACP bridge, then inspect how the harness invokes `buzz messages send` and handles the missing BUZZ_PRIVATE_KEY. Determine whether Gateway-backed ACP is supported and document a secure configuration; done means replies publish without exposing or pasting the private key into OpenClaw.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai-infra-agents, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100