Skip to content

Agent unable to access workspace context despite user using @workspace and @folder mentions #6306

@LoZeno

Description

@LoZeno

Steps to Reproduce:

  1. User pinned @workspace to provide context for updating Refit ISecurityDomainClient interfaces
  2. Agent failed to see any tags in the message
  3. User explicitly pinned three folders: @Domain, @Domain.Client, @Domain.Client.V2
  4. Agent still could not see any tags with file contents
  5. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugWe can reproduce the issue and confirmed it is a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions