GitHub Copilot Spaces: organizing chat context for repeated workflows
Published 2026-01-10 by Owner
GitHub shipped Copilot Spaces in late 2025. The feature lets you save a curated set of files, repos, and instructions as a reusable “Space.” For specific repeated workflows, this is meaningful.
What Spaces are
A Space is:
- A set of files (from any GitHub repo you can access)
- Optional custom instructions specific to this Space
- Optional reference docs (Markdown, PDFs, etc.)
- A name and description
You activate a Space in Copilot Chat; the Space’s context applies to that conversation.
A specific use case
For a team I work with, a useful Space:
Name: “Production Incident Investigation”
Files:
runbooks/incidents.mdservices/monitoring/dashboards.mdlib/error-codes.ts- The last 3 incident postmortems
Instructions: “Help with active incident investigation. Reference the runbook for procedures. Use error codes from error-codes.ts. When suggesting actions, cite specific runbook sections.”
When an incident hits, the on-call engineer activates this Space and gets Copilot grounded in the team’s actual incident response procedures rather than generic suggestions.
Other useful Space patterns
A few patterns that work:
Onboarding Space. Files: architecture diagrams, getting-started docs, CLAUDE.md. New engineers get oriented context.
Code review Space. Files: code review guidelines, common pitfalls. Reviewers get team-specific review focus.
Planning Space. Files: roadmap, current quarter’s priorities, recent design docs. Planning conversations are grounded in current direction.
Migration Space. When doing a major migration: files relevant to the migration, the migration spec, current status. Coherent context across many migration sessions.
Comparison to alternatives
Vs. just pinning files in chat: Spaces are persistent; pinning is per-conversation. For workflows you do repeatedly, Spaces save the setup time.
Vs. CLAUDE.md or .cursorrules: Project-level rules apply to all work in the repo. Spaces are workflow-specific. Both have a place.
Vs. custom instructions per repo: Custom instructions apply to all chat in a repo. Spaces are scoped to specific use cases. More granular.
The pattern: Spaces are for “this specific kind of conversation needs this specific context.” Other mechanisms cover the broader cases.
What’s missing
A few capabilities I’d want:
Sharing Spaces across an org. Currently Spaces are per-user. A team-shared Space registry would be useful.
Auto-activation. When a conversation starts that matches a Space’s purpose, auto-suggest activation. Currently the user has to remember to activate.
Space templates. Standard Spaces shipped with Copilot for common patterns. Onboarding, code review, planning — would help users get started.
Analytics. Which Spaces get used? Which ones are dormant? Helpful for cleanup.
These are reasonable next steps. The current implementation is useful but minimal.
Worth using?
For Copilot users with recurring workflows where context matters: yes. Setup is 15 minutes per Space; ongoing benefit is real.
For occasional Copilot users: probably not. The setup cost outweighs the benefit.
For teams: have a discussion about which workflows would benefit from shared context. The patterns above are starting points; your team probably has others.
Adoption
Spaces are part of Copilot Business and Enterprise. Pro tier doesn’t have them.
For organizations on Business+: Spaces are included; no extra cost. The activation step is “use the feature.” Many teams haven’t yet.
If your team has been using custom instructions or pinned files repeatedly for the same workflows, Spaces is the more durable pattern. The migration is straightforward.
