Open
Description
Problem
Amazon Q's pinned context feature currently does not detect files or directories that were created after launching VSCode. This creates a mismatch between the actual workspace and what Amazon Q can access, leading to workflow disruptions and confusion.
Steps to Reproduce
- Create a file or directory outside VSCode (e.g., via the command line or file explorer).
- Launch VSCode and open the workspace containing the new file/directory.
- Open Amazon Q and try to reference the file using
@filenameor@foldername. - Observe that Amazon Q does not recognize or access the newly created item.
Expected Behavior
Amazon Q should:
- Automatically detect new files and folders created after VSCode is launched.
- Allow seamless use of
@fileand@folderreferences for all workspace content. - Stay in sync with the actual file system without requiring user intervention.
- Offer a consistent and up-to-date developer experience.
Current Behavior
- Files/folders created after launching VSCode are invisible to Amazon Q pinned context.
- Developers must restart VSCode or manually open files for Amazon Q to register them.
- Leads to confusion, delays, and repetitive workarounds.
Impact
- 🔁 Workflow Disruption: Restarting VSCode interrupts developer flow.
⚠️ Inconsistent Context: Amazon Q operates on a stale view of the project.- 🛠 Manual Fixes: Users must interact with each new file to include it.
- ❓ User Confusion: No clear indication of why files aren't accessible.
System Details
- Operating System: Windows 10
- Visual Studio Code version: 1.101.1
- AWS Toolkit version: 3.66.0
- Amazon Q version: 1.77.0
- Workspace Type: Local
Additional Context
This issue is especially impactful for:
- Developers using CLI tools or other editors alongside VSCode.
- Teams collaborating with external file sync/build pipelines.
- Workflows involving generated or dynamically created files.