Skip to content

Explain workspace denials on delegated workstations - #32

Closed
nathan-thillairajah wants to merge 2 commits into
mainfrom
eggy/workstation-workspace-mismatch
Closed

nathan-thillairajah wants to merge 2 commits into
mainfrom
eggy/workstation-workspace-mismatch

Conversation

@nathan-thillairajah

@nathan-thillairajah nathan-thillairajah commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

On a Blox workstation, a 403 workspace_mismatch now tells the agent to ask the owner to switch workspaces, instead of passing through a server hint it can't act on.

The delegated workstation credential acts in whatever workspace the owner most recently signed into or switched to in BuilderLab. If they move to another workspace somewhere else, the workstation's existing apps return workspace_mismatch. The server's next_action says "use a credential for the workspace that owns this app", and the generic 403 fallback suggests bl workspace switch. Neither works on a workstation, because switch needs a local session and org config.

Changes (proxy credentials only):

  • workspace_mismatch: run bl workspace list, ask the owner to switch to the app's workspace, don't create a replacement app.
  • Other 403s still use the server's next_action when there is one. The fallback no longer mentions bl workspace switch.

Session-authenticated behavior is unchanged.

Not covered here: a 401 on a workstation still suggests bl auth logout / bl auth login, which has the same problem. I left that out to keep this small.

Tested with a new process test covering mismatch, a generic 403, and owner_required passthrough. just check passes.

🤖 Generated with Claude Code

nathan-thillairajah and others added 2 commits October 23, 2026 13:37
A delegated workstation credential acts in the workspace its owner most
recently selected in BuilderLab. When that selection changes, app requests
return 403 workspace_mismatch, and the generic recovery pointed at
`bl workspace switch`, which needs a local session a workstation does not
have. Tell the agent to report the active workspace and ask the owner to
switch in BuilderLab instead, and keep explicit server guidance for other
denials.

Co-authored-by: eggy <efcb1558faef42d4f7318ed532141edb57bcc52dbc8a92ae8c35637b8a5c3ff6@remote-agent-pilot.communities.buzz.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: eggy <efcb1558faef42d4f7318ed532141edb57bcc52dbc8a92ae8c35637b8a5c3ff6@remote-agent-pilot.communities.buzz.xyz>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nathan-thillairajah

Copy link
Copy Markdown
Contributor Author

🤖 Closing: accounts now belong to exactly one workspace and workspace switching is blocked, so delegated workstations shouldn't hit workspace_mismatch this way anymore. Companion skill PR squareup/builderbot-built-in-skills#22 is closed too.

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