Repository navigation
fix(workspace): show shared agents in sidebar - #791
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Shared agents were usable but absent from the sidebar because it filtered exclusively by ownership. Rename the section to “Agents” and show owned agents alongside agents the backend permits the current viewer to contact directly, in both desktop and mobile navigation.
Use the viewer-specific
canStartThreadpermission rather than the general sharing flag: thread-only visibility or sharing with someone else must not imply direct access. Keep removed agents hidden and retain offline agents. Update English and Chinese labels.Validation: four focused roster/rendering tests passed, covering shared visibility, revocation, private/thread-only exclusion, and existing navigation/unread behavior. Clean TypeScript checking passed with incremental caching disabled (the initial cached run reported a stale error in unchanged code).