-
Notifications
You must be signed in to change notification settings - Fork 287
Agent unable to access workspace context despite user using @workspace and @folder mentions #6306
Copy link
Copy link
Open
Labels
bugWe can reproduce the issue and confirmed it is a bug.We can reproduce the issue and confirmed it is a bug.
Description
Steps to Reproduce:
- User pinned @workspace to provide context for updating Refit ISecurityDomainClient interfaces
- Agent failed to see any tags in the message
- User explicitly pinned three folders: @Domain, @Domain.Client, @Domain.Client.V2
- Agent still could not see any tags with file contents
- User tried @workspace again - still no context visible to agent
Expected Behavior:
When user mentions @workspace or @folder, the relevant files should be included in or tags that the agent can read
Actual Behavior:
Agent received no workspace context tags despite multiple attempts by user to pin workspace and specific folders. Agent only saw tag but no workspace/file context for the pinned items.
Impact:
Agent was completely unable to complete the task of updating ISecurityDomainClient interfaces with controller endpoints because it couldn't access any of the necessary files from the workspace context.
Environment:
Windows 11
IDE: Rider 2025.3.3 Amazon Q plugin
Agentic-coding: ON mode
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugWe can reproduce the issue and confirmed it is a bug.We can reproduce the issue and confirmed it is a bug.