Notifications
Clear all
Amazon Q Developer Reviews
1
Posts
1
Users
0
Reactions
0
Views
Topic starter
30/07/2026 7:35 am
Tried Amazon Q Developer on our monorepo (multiple services, shared libs, custom tooling). Initial file suggestions were okay, but cross-service dependencies tripped it up.
It seems to index files independently, not grasp the actual workspace topology. When I asked for a deployment config for a specific service, it pulled in unrelated paths from a completely different part of the tree.
Has anyone gotten it to correctly recognize:
* Internal package references?
* Build tool context (like Turborepo or Nx)?
* Which service a given Dockerfile is for?
Or is it just doing pattern matching on file names?