GitHub Copilot Knowledge Bases Were Retired: Use Spaces for Team Context
🔍 WiseChecker

GitHub Copilot Knowledge Bases Were Retired: Use Spaces for Team Context

If an older guide tells you to open Copilot → Knowledge bases, stop looking for that setup screen. GitHub retired Copilot knowledge bases on November 1, 2025 and directs users to Copilot Spaces. You can still give Copilot curated internal documentation and code context, but the current workflow is different. GitHub’s retirement notice explains the change.

ADVERTISEMENT

What Replaces Copilot Knowledge Bases?

Spaces collect sources and instructions for a particular task or project. Use one for an internal API, onboarding material or a release’s design decisions. This is retrieved context for Copilot responses, not training a private model and not a guarantee that every inline code completion automatically uses the space.

GitHub-backed sources update as their source material changes. Do not apply the former article’s invented 24-hour indexing schedule or look for a “Refresh all” knowledge-base control. See what Spaces support.

Check Access and Decide Who Owns the Space

Spaces are available to people with a Copilot license, including Copilot Free, subject to applicable policies. An Enterprise upgrade is not a universal prerequisite. Questions still consume the applicable Chat usage allowance or AI credits.

For team material, decide which organization should own the space and who maintains it. Confirm that intended readers can access the underlying repositories. Sharing a space does not grant access to a private source they could not otherwise open.

Do not add a GitHub account named github-copilot as a repository collaborator based on an old tutorial. That is not a step in the documented Spaces setup.

ADVERTISEMENT

Create a Space and Add Focused Sources

  1. Open Copilot Spaces and choose Create space.
  2. Name the space and select yourself or an eligible organization as owner. Create it.
  3. Add instructions describing the task, source priorities and boundaries. For example: “Answer questions about our payments client using the attached API reference. If a behavior is not documented, say what is missing.”
  4. Choose Add sources and add the relevant GitHub files, repository, issues, pull requests, uploaded documents or text.
  5. Ask a narrow question whose answer you can verify, such as which documented function retries a failed payment. Compare the answer with the actual source.

A repository is searched for relevant material; it is not loaded whole into every answer. Attach a few specific files when those documents must be consistently available. Detailed controls are in GitHub’s creation guide.

Use Space Context in a Supported IDE

The IDE route uses the remote GitHub MCP server, not automatic background attachment to all completions. Enable its copilot_spaces toolset, which is not included by default, and use a tool-capable Agent chat. Confirm list_copilot_spaces and get_copilot_space are enabled.

Name both the space and its owner in your request. For example: “Use the Payments API space owned by our organization to explain the retry flow. Do not modify files.” Follow the official IDE setup for your editor’s configuration.

There is an important difference from the web experience: repository-level context and uploaded files are not currently supported through Spaces in the IDE. GitHub files, issues, pull requests, added text and instructions are supported. If something is missing, check the source type before changing access permissions.

ADVERTISEMENT

Share Team Knowledge Without Broadening Access Unnecessarily

Use the space’s sharing control to add the intended people or teams. Organization spaces offer viewer, editor and admin roles, plus a base role for other members. Give editing or administrative rights only to maintainers. A private source remains subject to its own permissions. See Spaces sharing roles.

Keep secrets, production credentials and unrelated customer records out of the sources. A space intended for onboarding should not become an uncontrolled dump of every internal repository.

Verify the Context Before Relying on an Answer

Keep a short acceptance check: one API question, one policy question and one question the sources cannot answer. Confirm the first two against source files and make sure the third does not produce an invented answer. Repeat after a material source change or permissions change.

If an answer is stale, inspect the source it actually used, its current contents, and whether the reader can access it. If an IDE response lacks a document, compare with the web space and the IDE source-type restrictions. Do not “fix” missing context by granting a new service account broad repository access.

Official documentation checked: October 14, 2026.

ADVERTISEMENT

Did this guide solve your problem?