-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Custom MCP config gone when resuming a session #1929
Copy link
Copy link
Closed
Labels
area:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variablesarea:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registryMCP server configuration, discovery, connectivity, OAuth, policy, and registryarea:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session state
Description
Metadata
Metadata
Assignees
Labels
area:configurationConfig files, instruction files, settings, and environment variablesConfig files, instruction files, settings, and environment variablesarea:mcpMCP server configuration, discovery, connectivity, OAuth, policy, and registryMCP server configuration, discovery, connectivity, OAuth, policy, and registryarea:sessionsSession management, resume, history, session picker, and session stateSession management, resume, history, session picker, and session state
Type
Fields
Give feedbackNo fields configured for Bug.
Describe the bug
I start copilot via:
copilot --additional-mcp-config @.copilot/mcp-config.jsonThen in copilot, I resume a session via
/resume. It resumes the session but the MCPs are goneAffected version
GitHub Copilot CLI 1.0.2.
Steps to reproduce the behavior
Expected behavior
MCPs should either stay connected or general support for repository-based MCPs/directory based MCPs should be added
Additional context
No global mcp config in use (anymore) because too many MCPs use a lot of tokens, thats why I switched to use MCPs per repository