Introducing Copilot Spaces: A new way to work with context ✨

[Akash1134]

Copilot Spaces is a new feature within GitHub Copilot. You can organize and centralize relevant content—like code, docs, files, and (soon) issues—into “Spaces” that ground Copilot’s responses in the right context for a specific task.

Key Features ✨

Create a space

• Organize code, docs, files, and other project context into a space.
• Add custom instructions to help guide responses.
• We’ve made some adjustments to how Copilot works with context in Spaces, so context groundedness should be very high.
• Context is always based on the latest state of your main branch.

Chat with a space

• Ask Copilot questions grounded in the context of your Space for more accurate and relevant answers.

Share it with teammates

• You can share spaces with other members of your organization.

Some of our favorite use cases ⭐

• Answering questions about code: Chris Westra is an engineer on the Spaces team. He grouped all of the code associated with Spaces and added video transcripts from a recorded Spaces session. We use this Space to answer questions about how Spaces works under-the-hood (very meta). 🙂

• Standardizing coding standards and best practices: Rahul Zhade works on a team that advises engineers on secure coding practices. He often answers the same questions over-and-over again in Slack, so he set up a Space. It contains the documentation for our standard auth model, how to do cryptography as well as instructions on how to go through the security review process.

• Writing SQL/KQL queries: Kelly Henckel is a product manager who is very good at writing SQL and KQL queries. She’s created spaces designed to help people self-service writing data queries and creating dashboards. These helpers contain the code for our telemetry schemas as well as example queries.

• Updating documentation: Holly Kassel is a product manager working on billing and licensing. She’s been updating GitHub’s documentation to be more user-friendly based on questions arriving through our customer support channels and discussion posts. She creates spaces for each new batch of documentation which needs to be updated, links the existing code and documentation hosted in GitHub, and adds instructions and frequently asked questions as context. The space generates updated versions of the documentation which can be easily copied into our docs repo.

And more We’ve also been having fun with them. Hubbers created a personal finance space for answering questions about vesting and other benefits, an offsite space for consolidating travel information, and a wombat Space for, uh, wombats? Anyways…

Please share feedback with us 🤝

This is an early preview, so we appreciate your feedback. Give spaces a try and let us know what you think either in this discussion post or through the inline feedback button.

Go to Spaces 🚀

• See the detailed changelog post.
• Learn more about spaces in our documentation on Copilot Spaces.

[JoostVoskuil]

Wow... this was unexpected and very nice.

It seems that I can only select owners as organisations where Copilot Access (to distribute seats) is enabled. I can't see the other organisations. I would expect that this is separate (same as the Coding Agent) policy where license distribution and organization settings are two separate things.

[albertjohn3]

This feels like a huge step forward—finally, context that actually sticks and 7 Brew menu scales with the team. Excited to try it out!

[christopherboard]

Looks good! Adding additional sources in future will be needed for greater adoption and scaling. For us, examples would be Confluence and Jira.

[khenckel]

Glad to hear it Christopher! We're thinking about an MCP integration where you could connect Spaces with 3P servers for Confluence/JIRA/etc.

[christopherboard]

Sounds good. After using this a bit over past 24 hours, I think for an Enterprise like ours, we would for sure need MCP server integration for our other CI/CD/Agile tools with Jira and Confluence being big ones, along with being able to bring in more docs/code from a repo into the space as well. the 50 file limit, based on how our projects are broken down and organized, makes it painful for us to select the right scope for the spaces context. Ideally I could just select a whole repo, as well as some other docs/tickets and then that would give me a fantastic context to leverage this.

[tmpduarte]

indeed, allowing this to integrate with external tools that host documentation (e.g.: notion) would massively increase the context

[sarthakpati]

This is awesome! It would be great if you could support >50 files directly, though. 😄

[khenckel]

And there is no way to break it down @sarthakpati ? There are no subsystems within the project?

[sarthakpati]

There are, but even the sub-systems are larger than 50 files.

[khenckel]

Makes sense! We're working on removing the file count limit to start with (or at least making it a lot higher). We should have something to play with soon.

[brooke-hamilton]

We need the full context of a whole repo in order for Spaces to be useful. Where most of the GitHub copilot tools break down is in not having the full context of the whole repo.

[sarthakpati]

Thanks you so much, @khenckel!

[russeg]

how do i delete all the conversations? only way i see is to go to "..." then delete each one manually

[khenckel]

Unfortunately, that is the only way to do it. :/ May I ask what happened and why you'd like to delete all conversations?

[Raventh23]

is there any plan for Copilot Spaces to be reachable through Copilot in the IDE?

[khenckel]

Absolutely! We're starting work on this now.

[assafbem]

Absolutely! We're starting work on this now.

When that planned to be delievered? Thanks
It is totally needed

[concaoccc]

@khenckel is there any time about how to support this through Copilot in the IDE?

[andrzejressel]

Will it be possible to share non-organizational Copilot Spaces? I like having my project's docs in there, but currently I'm the only one who can use it.

[khenckel]

Great idea, are you thinking with other specific users?

[andrzejressel]

Nobody in particular - I would like this Copilot Spaces to be alternative way of reading documentation for all users.

[khenckel]

Like a public Space?

[davidcraig5]

It seems like these should be managed like repos, being able to add users and teams.

[warengonzaga]

Is there a way to use spaces within the VS Code Copilot Extension? I always struggle with Copilot as I work on multiple projects at once and I want to share the details of two repos into one chat. So this maybe solve it having a space for both repo to share context?

[khenckel]

Great idea! We're getting started on this now! 🎉

[zsakmany]

Came here for this :) it would be a great feat to link the extension to a specific space I have. So I can run it in agent mode with all the knowledge in the space.

[aslafy-z]

This is really nice, awesome additions would be:

• whole repo selection without the need from selecting files one by one
• ways to add more context like pull requests/issues/commit infos
• agentic workflows with MCP support (open pull requests...)

[FrostyDSnowman]

Will we be able to include MSTeams' recordings to provide additional documentation and context? Will the meetings be accessible by CoPilot?

[khenckel]

Great idea. We'll support file uploads soon, but not sure about a direct integration yet.

[aoi1]

Hello! I'm really excited about this feature! Being able to call Copilot Spaces from the API would be incredibly helpful, as it would allow us to use it from Slack as well!

[khenckel]

Are you thinking of calling a chat API or CRUD API?

[AndreaGriffiths11]

This is so cool! Very excited to use it personally

[khenckel]

Please let us know how you're using them @AndreaGriffiths11! It's such an early preview and all feedback is incredibly valuable for shaping the future direction.

[htekdev]

I would like to see copilot spaces work with GitHub Coding Agent and event Copilot Chat. If you can either provide coding agent the ability to grab from organization or personal spaces, you can have coding agent have smaller context in tasking by referencing some space.

We need this for our enterprise since we have enterprise standards for certain tasks and if folks can just create an issue referencing that standard to apply to their repo and assign to copilot that would be game changing!!!!!

I foresee an issue body like this.

Go through the guide found in `Code Space Link`.

[AYABD]

I absolutely share the same thought, add to that:
-the ability of the coding agent to read images uploaded to an issue's description would be even better (because right now it doesn't seem like the coding agent is taking into context images when you assign it to an issue).

[hectorlaris]

I always trusted GitHub to do it! Thanks.

[OleKristianH]

Having both Knowledge Bases and Spaces is confusing since Knowledge Bases are simply a subset of Spaces. They should be unified into a single system with different modes, even if they operate differently behind the scenes.

[sandstrom]

This is great news! 🎉

Some things to make it more useful for us:

1. Access via IDE (VS Code) -- I read this is being worked on.
2. Being able to append files/context via an API, so basically CRUD API access (not API access to chat interface). This would allow us to append/update build artifacts (docs are sometimes not in source, but produced as artifacts during a build pipeline run).

• For this to be useful, it would be nice if we could give each context/file/attachment a unique key [string], along with the name (human label). Such unique keys are great for doing 'upsert', i.e. add-or-update during CI runs.

3. An alternative to 2 would be allowing us to attach release artifacts as context, but I think this is less flexible and probably a lesser approach than 2 above.
4. Would be nice if attachments could be pattern/regex just as with enterprise knowledge bases.

[tworivers5]

Hey what's up? I'm sorry I have no clue what I'm doing.

[jholeo]

I have the following feedback:

• Increase the file size limit. Currently, you can only add around 529 KBs. 1 to 15 MBs would be better
• Allow to share spaces between teams and add sorting and search options for when too many spaces cover the screen
• Add an option to group spaces based on teams, topics, or custom properties
• Do changes to existing repo files in an space get automatically updated? If not, this would be a nice feature/setting to add
• If everybody in my company starts creating spaces, the list of spaces can get flooded quickly. Adding an option for draft spaces needed to be approved by an org admin or custom repo role would be great.
• Allow to select which files from a space can be deleted

[rantoniuk]

As an open-source maintainer working on several repositories within one GH organisation, it seems weird that I can "only" add issues or PRs and not e.g. a repository or organisation - but maybe I'm missing something here?

Create spaces to organize and centralize relevant content that grounds Copilot’s responses in the right context for a specific task

So this is exactly what I need - I need the Space to have in the context the "core" repository of a project, so that when I am refactoring a child plugin, it pulls the latest practices or APIs from the core.

[oshriza]

VERY NICE!

Please improve with:

1. We in Enterprise account, I created space in 'MYORG' as owner of the space, I want to share other organizations or the entire enterprise to use this space. Think of central documentation that we have.
2. File size limit is very limited!
3. Currently I see that space can only create issues, what about changing code and create PR (instead of use it from issue - assign to copilot), feels more natural for me.

[tobiashochguertel]

Is there a way to get more storage because I just reached already 44% of the attachment limit with a few markdown files for 3 Spaces?

[cynthiateeters]

Use case: Copilot Spaces for GitHub Education Classroom

I belong to a group of three who teach multiple courses using GitHub Classroom under a dedicated Education organization. All assignment repos live in that org and I will be having my students get Copilot Pro via the Student Pack. As instructors, we also have Copilot Pro through GitHub Education.

We see huge potential in Copilot Spaces to:

• Bundle assignment specs, starter code, and instructions into one “Space”
• Give students consistent, curated context when they open Copilot Chat
• Ensure everyone (instructors and TAs) refers to the same materials

The problem:
When I try to create a Space, only orgs with Copilot seat-management enabled appear. Our Education org doesn’t show up, so we can’t register Spaces, even though all our repos and seats already live in that org via Classroom.

Impact:

• Instructors can’t set up Spaces for assignments
• Students miss out on context-aware assistance tailored to each exercise
• We lose reproducibility and consistency across sections

Request:
Please enable Education organizations (using GitHub Classroom and Student Pack licenses) to create and manage Copilot Spaces independently of the seat-distribution settings. That way, we can keep all teaching workflows neatly inside our Classroom org.

Thank you!

[rserrato-pdl]

This is an amazing feature!! I am just getting started and trying to use it in my organization. A question, will there be a way I can interact with more than one space in a conversation? for example if I have a space that has expertise in one topic and another that is expert in a different one, could I chat with both contexts in the same conversation? I think that would be very useful for large organizations where you have multiple sub-orgs each of them with their own business domains, technology stacks, standards, etc. Example, I ask the business domain expert about the current state of requirements or features of a system, then I ask the coding and testing standards expert to create the code component with tests, finally I ask the expert on CD to create the pipelines for the deployment of the application to the different environments. I know this could be approached with a monolithic space, or you could generate outputs from one space that you later import in a different one in a chained fashion, but I think having the ability to interact with many of them in the same session would be great to have. Thanks.

[andrey-dubnik]

I would have to be able to link multiple repositories (+ discussions, issues, PRs) to a space to narrow down the data, this can be super helpful while dealing with:

• common issue troubleshooting which may come from the docs, discussions, etc.
• answering the questions about the product, again multiple possible sources of data
• code generation
• etc.

I should also be able to only add files by type e.g. *.md flies only e.g. write some sort of a .gitignore file for each repository I'm including. This would help to filter out the "junk" which may otherwise bloat the context.

[kitswas]

Copilot Spaces currently does not have access to tools to:

• Fetch data from the GitHub API (or any public API, even if I provide the link)
• Perform web searches
• Access real-time repository information

So... what can it do?

Most of the potential use cases need the user to feed data manually to the model.
It badly needs the capability to send a GET request and read the response. And do web searches.
Even the free AI that comes with search engines can do better.

[brian-olson-usps]

Very nice feature. I would like to add categorization / tagging to the GitHub Space.

For example,

• A Terraform Space would be tagged with #Ops
• A Linting Space would be tagged with #Dev and #Security
• An Accessibility Space (e.g., section 508) would be tagged with #Dev

Then a person can search and filter Spaces based on the tags or display entire categories.

[nnellanspdl]

I couldn't find this in the docs. Sorry if I missed this somewhere. What is the current size limit for a Space? I've added a little over 100 files to my Space and I'm sitting at 108% usage.

[LasseHels]

Great feature. I would like:

• The ability to add all GitHub issues with a specific tag to a space. My team has years of reliability investigations in GitHub issues, and we would like to create a "reliability space" that engineers can use to debug new reliability issues with past knowledge. Right now, we have to manually add and maintain the list of issues attached to the space. It would be easier if we could configure the space to include all issues tagged Reliability. That way, tagging an issue with Reliability automatically adds it to the space, and removing the Reliability tag from an issue automatically removes it from the space.
• Spaces HTTP API with endpoints for:
  • Creating a space.
  • Deleting a space.
  • Getting a space.
  • Adding files to a space.
  • Removing files from a space.
  • Gauging space usage. Is anyone querying the space? Are they getting the answers they want?

[LarissaSilvaFernandes]

Copilot Spaces: It's a new way to collaborate and work with shared context. Interesting!