feat(desktop): add OpenClaw native ACP runtime - #3868
Conversation
|
big surface. could you split the install/verify bits from the catalog entry so the scary spawn-boundary changes are easier to review alone? |
3c4468a to
35e495d
Compare
|
split as requested.
GitHub cannot select a fork branch as the base of an upstream PR, so #3868 must |
35e495d to
859019c
Compare
daebf1e to
c3976a1
Compare
Signed-off-by: Vincent Koc <vincentkoc@ieee.org>
c3976a1 to
61fadb7
Compare
Final maintainer handoverThis PR is the Buzz side of OpenClaw's native ACP integration:
The temporary generic Buzz split, #4238, is closed. Review Buzz contract
Security and lifecycle
Final heads and proof
Do not ship the Buzz runtime until a compatible OpenClaw release containing |
Summary
openclaw-acpnative stdio executable with zero argumentsopenclaw models status --check --jsonThere is no OpenClaw Gateway lifecycle, URL/token handling, companion node, or OpenClaw-specific process manager in Buzz.
The temporary generic split PR, #4238, is closed. This PR is the self-contained Buzz change and includes the generic managed-runtime contracts required by the OpenClaw registration.
Runtime Contract
openclaw-acpis the native-capability marker. Its process owns the OpenClaw model loop and tools, so the dedicated agent's inheritedBUZZ_*environment reaches permitted local tool execution and the Buzz CLI used to publish signed replies.OpenClaw treats host-forwarded ACP prompts as non-owner ingress. Owner-only OpenClaw tools remain unavailable; exec and plugin operations use ACP permission requests and fail closed.
Older Gateway-only OpenClaw releases do not expose
openclaw-acpand are not detected as compatible.Migration Contract
At startup, Buzz rewrites only the exact previously shipped OpenClaw preset shape:
openclaw["acp"]openclawThat shape becomes
openclaw-acpwith zero arguments. Custom paths, custom arguments, and other user overrides remain untouched.The visible terminal-auth launcher preserves Buzz's augmented
PATHon macOS, Linux, and Windows so managed runtime binaries remain discoverable during authentication.Dependency Stack
openclaw-acpexecutable.Do not ship this PR until a compatible OpenClaw release is available.
Related Issue
Testing
cargo fmt --all -- --checkgit diff --checkbuzz-acpargument normalization: 1 passed61fadb7e4cd1525ab3f3c40eb813ee78a0d7bd6dRemaining Live Proof
The OpenClaw dependency stack passes focused tests and changed-surface validation. A clean Testbox has no usable OpenAI authentication, so a real Buzz mention/signed-reply round trip remains required on an authenticated Crabbox before release.