Skip to content

fix(amazonq): keep memory bank and agent config writes inside the workspace folder - #3066

Draft
laileni-aws wants to merge 2 commits into
Amazon-Q-Developer:feature/laileni-fixesfrom
laileni-aws:fix/workspace-folder-boundary
Draft

laileni-aws wants to merge 2 commits into
Amazon-Q-Developer:feature/laileni-fixesfrom
laileni-aws:fix/workspace-folder-boundary

Conversation

@laileni-aws

Copy link
Copy Markdown
Collaborator

No description provided.

@codecov-commenter

codecov-commenter commented Nov 16, 2026 •

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 98.90110% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
.../language-server/agenticChat/tools/mcp/mcpUtils.ts 98.70% 0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

@laileni-aws
laileni-aws force-pushed the fix/workspace-folder-boundary branch from 55f3b6f to ff71f00 Compare November 17, 2026 04:23
…kspace folder

The memory bank cleanup and the agent config migration of a workspace folder now write only when
the path, after symbolic links are followed, is inside the workspace folder. Otherwise, or when
the path cannot be resolved, they write nothing and log a warning. Every migration call now
names the agent config that it writes.

Adds tests.
…pace folders

Checks that the migration writes nothing when the links of the workspace agent config cannot be
resolved, that each workspace folder is checked against its own agent config, and that the global
agent config is still written through a linked global agents folder.
@laileni-aws
laileni-aws changed the base branch from feature/security-fixes-v2 to feature/laileni-fixes November 18, 2026 20:38
@laileni-aws
laileni-aws force-pushed the fix/workspace-folder-boundary branch from 7bf9b2d to fd7ae3c Compare November 18, 2026 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants