# How Copilot Spaces gives your AI the right project context | GitHub Checkout

Source: https://www.youtube.com/watch?v=noVdaj7sEWA
Recap page: https://rapidrecap.app/video/noVdaj7sEWA
Generated: 2025-11-18T15:33:24.805+00:00

---
## Quick Overview

GitHub Copilot Spaces allow developers to bring the context of GitHub repositories, issues, and pull requests directly into the development environment, enabling the Copilot Coding Agent to provide context-aware suggestions, like generating code or reviewing PRs, which significantly improves workflow efficiency and security adherence for engineers and product managers. The key benefit is keeping all necessary information—code, documentation, and context—available immediately within the workspace without context switching.

**Key Points:**
- GitHub Copilot Spaces provide context by linking repositories, issues, and pull requests directly within the development environment.
- The context provided allows the Copilot Coding Agent to offer highly relevant suggestions for tasks like code generation and PR reviews.
- Spaces can be used collaboratively, allowing teams to share context and work together on specific issues or feature planning.
- Vanessa Kalu mentions upcoming features like public support and API access for Spaces, and support for additional file types like .docx and .pdf.
- The demonstration showed how a security issue (potential unsafe usage of check_call without shell=False) was debugged by linking the issue and relevant documentation files within the Space.
- The process involves attaching context (repos, issues, PRs) and then prompting Copilot to act as an experienced engineer to solve the problem, which is then reflected in the generated PR.
- Spaces are private by default, but users have control over sharing with specific individuals or organizations.

![Screenshot at 0:04: Vanessa Kalu explaining how Copilot needs context like files and pull requests to provide relevant responses within a Copilot Space.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-00-04.png)

**Context:** The video features an interview between Andrea Griffiths, a Developer Advocate at GitHub, and Vanessa Kalu, a Product Manager at GitHub, focusing on the capabilities and benefits of GitHub Copilot Spaces. The discussion centers on how Spaces enhance the developer workflow by providing immediate, context-rich information to the Copilot Coding Agent, making debugging and collaborative work more efficient, especially when tackling security issues like command injection risks.

## Detailed Analysis

Vanessa Kalu explains that GitHub Copilot Spaces integrate context, such as files, pull requests, and issues, directly into the development workspace, allowing the Copilot Coding Agent to operate with full project awareness. This context is crucial for generating accurate code suggestions and performing efficient debugging, as demonstrated by linking a security issue regarding unsafe subprocess calls to the space. Kalu highlighted that Spaces are private by default, offering control over collaboration, and that she uses them extensively for everything from feature planning to debugging. She detailed the process of linking the relevant GitHub issue (like issue #5 concerning command injection risks) and then prompting Copilot with specific instructions, like asking it to act as an experienced engineer to propose code changes. The resulting PR from Copilot directly reflects the context provided in the Space. Future roadmap items include expanding file type support (.docx, .pdf), public support for Spaces, and a dedicated API for Spaces to enable broader integration and collaboration across teams and organizations.

### Copilot Spaces Contextualization

- Copilot needs context from files, PRs, and issues
- Copilot responses are always grounded in the project context
- Context includes repos, files, issues, and PRs.

### Demonstration

- Debugging a command injection issue in build_generate_mady.py
- Context linked via PR URL
- Copilot generates a plan covering goal, approach, execution, and impact.

### Key Features & Future Roadmap

- Spaces are private by default but shareable
- Used for code generation and feature planning
- Upcoming features include image support, .docx/.pdf support, public spaces, and an API.

### Collaboration & Trust

- Knowledge sharing is collaborative within Spaces
- Teams use it for co-generation and planning
- Promotes trust among engineers and product managers.

![Screenshot at 0:01: The start of the discussion where Vanessa introduces the concept of bringing context to Copilot via Spaces.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-00-01.png)
![Screenshot at 0:14: Andrea Griffiths \(left\) and Vanessa Kalu \(right\) introducing themselves at the start of the interview.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-00-14.png)
![Screenshot at 0:51: The main interface of a Copilot Space, showing the title "CodeQL Security Review" and a list of 10 attached sources/files.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-00-51.png)
![Screenshot at 1:04: The demonstration begins by showing the specific GitHub Issue: "Potential unsafe usage of check\_call without shell=False #5".](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-01-04.png)
![Screenshot at 1:56: The process of adding context by pasting a GitHub URL for the issue into the 'Add via GitHub URL' dialog box.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-01-56.png)
![Screenshot at 3:35: Vanessa showing the detailed instructions provided to Copilot within the Space to guide its behavior as an engineer.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-03-35.png)
![Screenshot at 4:28: The Copilot chat interface receiving the prompt "Help me debug this attached issue" and starting to process the request.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-04-28.png)
![Screenshot at 5:33: The resulting output from Copilot detailing the goal, approach, execution steps, impact, and proposed changes for the security fix.](https://ss.rapidrecap.app/screens/noVdaj7sEWA/00-05-33.png)