AWS Q Feature Request

Question

I've noticed that AWS Q is workspace centric, not user centric. 
Now days, we work across multiple IDEs in mutiple environments. One day I may be coding locally on my laptop on a linux VS Code instance, tomorrow I'm in the AWS Cloud, and today I'm using PyCharm on a home server. Sure, but even excluding the different IDEs (ie: VS Code local, vs AWS Code Cloud) my request could work across...

Make AWS Q contexts USER centric, not workspace centric. I want to continue work I started on node A on node C when I boot it up (maybe node A has a specialty piece of hardware I want to test against, and node C has a beefy GPU... same codebase, same system, different tests... because I do a lot of multi-node parallelism)

re:Post Agent · Answer

Amazon Q Developer currently offers workspace context functionality, which allows it to index and understand your code files, configurations, and project structure within a specific workspace. The `@workspace` modifier helps Q Developer include relevant code chunks from your workspace as context for more accurate responses.

While your request for user-centric context across multiple environments and IDEs is understandable, the current implementation is workspace-focused. Amazon Q Developer does offer some features that partially address continuity across sessions:

1. Conversation persistence - You can pick up where you left off in conversations with Amazon Q Developer, even after closing the IDE or taking a break.

2. Conversation history search - You can locate specific past discussions using keywords.

3. Chat export - You can export chat sessions as markdown files, which could help transfer context between different environments.

However, these features don't fully provide the seamless user-centric context across different physical machines and IDEs that you're requesting. The ability to continue work started on one node (like your node A) on another node (like node C) with full context preservation isn't currently available as a built-in feature.

Amazon Q Developer is supported across multiple IDEs including VSCode, JetBrains IDEs, Eclipse, and Visual Studio, with workspace context functionality available in all of these environments. But the context doesn't automatically follow you across different physical machines or cloud environments.

Your feature request for making Amazon Q contexts user-centric rather than workspace-centric would indeed be a valuable enhancement for developers who work across multiple environments with the same codebase.  
**Sources**  
[Adding workspace context to Amazon Q Developer chat in the IDE - Amazon Q Developer](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/workspace-context.html)  
[Take control of your code with Amazon Q Developer’s new context features | AWS DevOps & Developer Productivity Blog](https://aws.amazon.com/blogs/devops/amazon-q-developers-new-context-features/)  
[Continue to take control over your code with Amazon Q Developer’s new context features | AWS DevOps & Developer Productivity Blog](https://aws.amazon.com/blogs/devops/continue-to-take-control-over-your-code-with-amazon-q-developers-new-context-features/)  
[Using Amazon Q Developer in the IDE - Amazon Q Developer](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/q-in-IDE.html)

AWS Q Feature Request

Add your answer

Relevant content