Skip to content

Buzz Updates

What changed—and what it means for operators

Meaningful Buzz changes, translated into operator impact, required action, and a clear evidence boundary.

Desktop v0.5.9DOCUMENTED UPSTREAM / NOT LOCALLY REPRODUCED

Buzz Desktop v0.5.9 restored private-channel member invitations

What changed

Buzz Desktop v0.5.9 includes the merged change that restores private-channel invitations for every active member. Owner/admin-only enforcement remains in place for elevated role grants, active role changes, and removals.

Operator impact

If an ordinary active member could not invite another ordinary participant to a private channel, v0.5.9 contains a fix for that path. This is a restoration of expected invitation behavior, not a new permissions model or proof that unrelated agent visibility, identity, or runtime problems are fixed.

Who is affected

  • Operators using private Buzz channels
  • Active members inviting ordinary participants
  • Teams inviting member, guest, bot, or agent participants
  • Owners and admins preserving elevated-role controls

Action required

MAYBE / DEPENDS

If private-channel member invitations were failing in your environment, update through your normal Buzz deployment process to a version containing the v0.5.9 fix, then retry the ordinary invitation flow. If invitations already work and you are not changing versions, this source documents no special configuration step.

Evidence boundary

The release, merged pull request, and merge commit document this behavior upstream. Buzz Agent Hub has not independently reproduced the before-and-after invitation flow for this update.

Operator explainer video

Related operator help

Start Here

Follow the operator path before changing a working setup.

Open page →

Setup Checklist

Commission one Buzz agent in a bounded, verifiable sequence.

Open page →

Troubleshooting

Find the first missing layer when an agent stops working.

Open page →