-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Full support for multi-repo setups #2011
Copy link
Copy link
Open
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:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
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:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agentsPlugin system, marketplace, hooks, skills, extensions, and custom agents
Type
Fields
Give feedbackNo fields configured for Feature.
Coming from a multi-repo workspace setup for VS Code, there is a lot of friction getting Copilot CLI to have the same tooling and instructions as the agents running in the IDE, despite the close relationship.
With /add-dir or by starting in the parent directory, the Copilot CLI can work across repos, but only one directory seems to be used for:
some of these can be configured with flags and env-var, but it would be great to have some kind of parity with VS Code so that it does not matter if one is running Copilot one place or the other.
Related issues?
#1826