aws / aws/amazon-q-developer-cli

bug: mcp/tools not switching when using /agent swap

Open
#3,129 0 comments 1 reaction 0 assignees View on GitHub
bug q chat
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

WSL

### Expected behaviour

If I have 2 agents, let's call them "A" and "B". Agent A has access to certain MCP servers and Tools, A1, A2, ... Ax. Agent B has access to other MCP server and Tools B1, B2, ... Bx. Now I start a session with Q CLI with Agent A. It will load Agent A's MCPs and tools. Now I swap agents through /agent swap B. I would expect it would load Agent B's MCP Servers and Tools.

### Actual behaviour

Q switches the context to Agent B, but it keeps the MCPs and Tools from Agent A.

### Steps to reproduce

_No response_

### Environment

```yaml

```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.