Skip to content

fix(memory-proxy): allow members to select team-visible agents - #930

Draft
guomengjia618-dot wants to merge 1 commit into
TencentCloud:feat/server_teamfrom
guomengjia618-dot:fix/proxy-team-visible-agents-924
Draft

fix(memory-proxy): allow members to select team-visible agents#930
guomengjia618-dot wants to merge 1 commit into
TencentCloud:feat/server_teamfrom
guomengjia618-dot:fix/proxy-team-visible-agents-924

Conversation

@guomengjia618-dot

Copy link
Copy Markdown

Summary

  • Query active agents at team scope during CodeBuddy session initialization.
  • Allow team members to select agents they own and agents with visibility="team".
  • Keep private agents owned by other team members hidden.
  • Add a regression test covering owned private, team-visible, and other private agents.

Root cause

CodeBuddy session initialization passed the current user ID to MetadataClient.listAgents, which added an owner_user_id filter to the team query. Team-visible agents created by an admin or another member were therefore omitted, causing session initialization and downstream memory injection to be bypassed.

Impact

Team members can now select shared agents during CodeBuddy session initialization without gaining access to another member's private agents.

Testing

  • npm test in MemoryProxy
  • Targeted strict TypeScript check for the new selector and regression test

Fixes #924

Signed-off-by: guomengjia618-dot <guomengjia618@gmail.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.

[Bug] Team members cannot use team-visible agents in CodeBuddy session init; only admin/owner token works

1 participant