Github Copilot Coding Agent access to Copilot Spaces

[ahmedbham]

Select Topic Area

Question

Copilot Feature Area

Copilot Coding Agent

Body

I have specific Copilot Spaces created containing reference to specific set of files. When using Github Copilot Coding Agent, I want it to reference one or more of those specific Copilot Spaces.

How can I do it?

[anyexpjay]

You cannot explicitly tell GitHub Copilot Coding Agent to reference a specific Copilot Space.
As of now, Copilot Coding Agent does not support manually selecting or attaching Copilot Spaces.

🔍 Detailed Explanation

GitHub Copilot Coding Agent automatically decides what context to use.

Copilot Spaces are currently designed for human-driven chat interactions, not for agent-level configuration.

There is no command, setting, or flag that allows you to say:

“Use Copilot Space X and Y for this agent task.”

The agent:

Reads open files

Scans repository context

Uses nearby code and symbols

Applies implicit context, not user-selected spaces

⚠️ What Is Not Possible (Yet)

❌ Selecting a Copilot Space inside the Coding Agent
❌ Binding a Copilot Space to an agent session
❌ Forcing the agent to only use files from a Space

✅ Practical Workarounds (Recommended)

Until native support exists, you can do the following:

1️⃣ Keep Relevant Files Open

Copilot strongly prioritizes open files in the editor.

2️⃣ Reference Files Explicitly in Comments

Add comments like:

// Refer to auth-flow.md and user-permissions.ts

3️⃣ Create a “Context Index” File

Create a file like:

COPILOT_CONTEXT.md

List all files you want referenced. The agent will naturally pick it up.

4️⃣ Use Directory-Based Organization

Group space-related files in a single folder. Copilot uses directory proximity heavily.

🧠 Why This Limitation Exists

Copilot Spaces are currently:

Chat-level constructs

Not exposed to the agent runtime

Still evolving (feature gap, not a bug)

📌 Final Verdict

There is currently no supported way to make GitHub Copilot Coding Agent explicitly reference one or more Copilot Spaces.
You must rely on file context, comments, and repository structure instead.