Repository navigation
bl apps: fix outputs that misled agents on Blox workstations - #47
Merged
Merged
Conversation
- Drop the stale "community commands don't work from a Blox workstation yet" sentence from the community help. - Route `bl apps community list` through the Blox proxy on workstations that opt in to community sharing, so an agent can resolve a community by name without a local login. - Include the owner quota in a plain `bl apps list`. - Add `audience.member_count` (null, because Apps Platform doesn't report workspace size) and `audience.summary` to `bl apps get --json`. Co-authored-by: Irving B <6c4c50b3b6dee89feaca78ea87eb5c8fde651d2d7b39d6da8c9354ce7a34e313@remote-agent-pilot.communities.buzz.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A plain `bl apps list` reads the owned listing for its quota with the same 3 minute timeout as every other control plane call, so a hung read stalled the whole list. It now uses the 5 second limit that community name lookups already use, and drops quota quietly on timeout. Tests now also cover a hung owned read, an owned read without quota, community names resolved through the proxy on `get`, a Kgoose origin that isn't the workstation proxy, and the exact error when the opt-in is off. The README quota paragraph is rewrapped and mentions `--scope manageable`. Co-authored-by: Irving B <6c4c50b3b6dee89feaca78ea87eb5c8fde651d2d7b39d6da8c9354ce7a34e313@remote-agent-pilot.communities.buzz.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…is refused The community-sharing refusal only fires on a Blox workstation, where an agent can't run `bl auth login` or choose another `--base-url`. Drop that advice so the next step is just Share & manage. Co-authored-by: Irving B <6c4c50b3b6dee89feaca78ea87eb5c8fde651d2d7b39d6da8c9354ce7a34e313@remote-agent-pilot.communities.buzz.xyz> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kalvinnchau
approved these changes
Nov 5, 2026
kalvinnchau
left a comment
kalvinnchau
left a comment
There was a problem hiding this comment.
🤖 Code-only review: no actionable findings at c12b781. Reviewed the complete diff, proxy-origin/authentication guards, command dispatch and config resolution, supplementary request timeout/error handling, audience serialization, and process-test coverage. Quota enrichment preserves the original listing and fails open only for optional metadata; community lookup requires the exact opt-in and existing workstation origin check without sending a local session. The added tests exercise production command paths, including refusal and timeout cases. No tests, builds or live Blox flows were executed for this code-only review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two agents on bb-public Blox workstations used
bl appsfor a non-technical user, and several outputs sent them the wrong way. The community help still said community commands don't work from a workstation.community listneeded a local login the workstation doesn't have. A plainlisthid the app quota.getsaid "everyone in your workspace" for a one-member workspace.What changes:
community listgoes through the Blox proxy on workstations that setBL_APPS_COMMUNITY_SHARING=enabled, the same opt-in BOT-2527: share with communities through the Blox proxy where it's enabled #41 added for grant and revoke. Everywhere else it works as before.bl apps listand--scope manageablealso read the owned listing forquota. If that read fails or takes more than 5 seconds, the list prints without quota.bl apps get --jsonaddsaudience.summaryandaudience.member_count. Apps Platform doesn't report workspace size yet, so the count isnull.On opted-in workstations,
bl apps getalso shows community names instead of IDs, because its lookup uses the same proxy. That lookup can add up to 5 seconds.The Share & manage link keeps
workspace, because the portal ignores the link unless it has bothappandworkspace.🤖 Generated with Claude Code