Skip to content

bl apps: say community sharing is off on workstations without it - #52

Open
nathan-thillairajah wants to merge 2 commits into
mainfrom
markS/bb-block-community-refusal
Open

nathan-thillairajah wants to merge 2 commits into
mainfrom
markS/bb-block-community-refusal

Conversation

@nathan-thillairajah

@nathan-thillairajah nathan-thillairajah commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Blox workstations only share apps with Buzz communities when the operator sets BL_APPS_COMMUNITY_SHARING=enabled. bb-public does. bb-block doesn't, and won't: it's a single-tenant environment where an app's workspace already covers the whole organization, so workspace visibility is how you share there.

On a workstation without the opt-in, bl apps community grant and revoke already stopped with community_sharing_unavailable_through_proxy, but pointed the owner to Share & manage, which can't share with communities there either. bl apps community list was worse: it fell back to a local login the workstation never has and returned auth_required or org_required. Agents took that as a login problem and kept trying workarounds, ending with the user asking for an administrator's grant. Someone hit exactly this on bb-block this week and still couldn't share their app.

What changes

  • On an Apps workstation without the opt-in, community list refuses before making any request, with the same code grant and revoke use.
  • The refusal from all three commands now names only bl apps visibility APP_ID workspace as the next step, and no longer mentions Share & manage.
  • Workstations that opt in, and laptops, behave as before.

Tests: a new one for the list refusal (unset and non-enabled values), and the two portal-link refusal tests are replaced by one that checks the visibility next step with and without a known portal. just lint and just test pass.

🤖 Generated with Claude Code

On a Blox workstation that hasn't opted in to community sharing (no
BL_APPS_COMMUNITY_SHARING=enabled), `bl apps community list` fell back
to a local login the workstation never has and reported `auth_required`
or `org_required`. Agents read that as a login problem and went looking
for workarounds, such as the skill's relay fallback, that end in a 403.

`list` now refuses up front with `community_sharing_unavailable_through_proxy`,
the same code grant and revoke already use, and both messages point to
`bl apps visibility APP_ID workspace` as the way to let others open the app.

Co-authored-by: Mark S <f24e6a2707dedca50330ec50ca75720a5691b529f8d8303f51c2feb08d1c906d@remote-agent-pilot.communities.buzz.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nathan-thillairajah
nathan-thillairajah requested a review from a team as a code owner November 17, 2026 16:24
Where a workstation can't share with communities, Share & manage can't
either, so sending the owner there was another dead end. The refusal from
community list, grant and revoke now names only
`bl apps visibility APP_ID workspace`.

Co-authored-by: Mark S <f24e6a2707dedca50330ec50ca75720a5691b529f8d8303f51c2feb08d1c906d@remote-agent-pilot.communities.buzz.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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