fix(site): show cross-org workspaces as disabled in chat picker#24944
Merged
Conversation
…chat picker Previously, workspaces from organizations other than the chat's organization were silently filtered out of the workspace attachment picker. Users had no indication why a workspace was missing. Show all user workspaces in the picker. Workspaces from a different organization are rendered as disabled with a tooltip explaining that the chat and workspace must be in the same organization.
DanielleMaywood
approved these changes
May 5, 2026
Contributor
DanielleMaywood
left a comment
There was a problem hiding this comment.
I think the code comments are low-value but other than that, LGTM
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
What does this solve?
When using Agents, I was trying to connect a chat I was using to my workspace. I was unable to find the workspace because it was in another organization as the chat. This was not made obvious, and I spent awhile looking through the docs on why a workspace might be unable to be attached.
This change makes all workspaces visible to the picker, with workspaces in other orgs disabled with a tooltip message saying why.
What changed
All user workspaces now appear in the picker. Workspaces from a different organization are rendered as disabled (greyed out, not selectable) with a tooltip on hover: "Chat and workspace must be in the same organization."
Changes:
filterWorkspaceOptionsByOrganizationfiltering; pass all workspaces to the picker insteadchatOrganizationIdprop threaded throughChatPageContenttoAgentChatInputWorkspacePickerListcomponent (used by both mobile and desktop pickers) that marks cross-org workspaces as disabled with a tooltipfilterWorkspaceOptionsByOrganizationfunction and its testsGenerated by Coder Agents
This PR was generated by Coder's AI agent based on a user report that workspaces from other organizations were invisible in the chat workspace picker, with no explanation for their absence.Examples
When in the
CoderorgWhen in my side org
On hover
Screencast.From.2026-05-04.14-28-23.webm