MCP tools unavailable after using /new command

[leonteq-dmytro]

Describe the bug

When starting a new conversation using the /new slash command, MCP tools that were available in the previous session (e.g., Jira MCP — mcp_atlassian_jira_get_issue) are no longer accessible in the new session.

Affected version

GitHub Copilot CLI v1.0.11

Steps to reproduce the behavior

1. Start copilot CLI with Jira MCP configured in ~/.copilot/mcp-config.json
2. Confirm Jira MCP tools are available (e.g., use mcp_atlassian_jira_get_issue)
3. Run /new to start a fresh conversation
4. Attempt to use any Jira MCP tool

Expected behavior

MCP tools should remain available across sessions, including those started with /new.

Additional context

• GitHub Copilot CLI v1.0.11
• macOS (Darwin)
• MCP: Atlassian Jira MCP server

[examon]

This should be resolved in v1.0.12 and later. MCP servers now reload correctly when switching sessions, which includes starting a new session with /new. If you still see this on v1.0.12 or newer, feel free to reopen this issue.