Skip to content

chore(buzz-acp): repin the fork to carry block/buzz#6101 (owner commands with mention text) - #787

Merged
jhgaylor merged 1 commit into
mainfrom
chore/buzz-acp-pin-fountain-2
Aug 17, 2026
Merged

chore(buzz-acp): repin the fork to carry block/buzz#6101 (owner commands with mention text)#787
jhgaylor merged 1 commit into
mainfrom
chore/buzz-acp-pin-fountain-2

Conversation

@jhgaylor

Copy link
Copy Markdown
Collaborator

Summary

Bumps the hosted buzz-acp fork pin so !rotate / !cancel / !shutdown work from the Buzz Desktop composer.

Observed on prod: @Fountain Maintainer !rotate reached the agent as a prompt ("Not sure what !rotate should do here"), and bare !rotate/!shutdown were dropped. Upstream issues: block/buzz#6014, block/buzz#6051.

#776 (repin to upstream) now also waits on block/buzz#6101.

Rollout note

Merging touches buzz-acp.source/.version, so buzz-acp-publish.yml and (after CI) build.yml run concurrently. If the image build races ahead of the release upload it fails on the download step — re-run build.yml (workflow_dispatch) once buzz-acp-v0.5.14-fountain.2 has both arches.

Test plan

  • buzz-acp-publish publishes buzz-acp-v0.5.14-fountain.2 with amd64 + arm64 assets
  • build.yml succeeds and Flux rolls the pods
  • From Desktop as owner: @Fountain Maintainer !rotate — no conversational reply, harness log shows the rotate

🤖 Generated with Claude Code

…nds with mention text)

buzz-acp.source -> jhgaylor/buzz@0bb9e5af (fountain-pin branch: the #6088
resume-sessions commits plus #6101, which lets is_owner_control_command
match !rotate/!cancel/!shutdown when the client renders the @mention into
the message body). Release name bumps to buzz-acp-v0.5.14-fountain.2 so the
image pulls the new build rather than a clobbered asset.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Jake Gaylor <jhgaylor@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant