.png){kind=small}
Copilot Spaces: What They Are and When to Use Them
Spaces as scoped context containers — GA September 2025.
What You Will Learn
- Explain what Spaces are.
- Decide when to use a Space.
- Distinguish Spaces from @workspace.
- Recognize plan availability.
- Build a use-case decision tree.
Why This Matters
Spaces (GA September 2025) are a new Copilot surface. Understanding when to use them vs @workspace prevents over-engineering and unlocks multi-repo and docs+code scenarios.
Concept Explained
A Space is a scoped context container that persists across conversations. You add repos, docs, and files to a Space; Copilot uses that curated context for all chats in the Space.
How It Works
Create a Space at github.com/copilot/spaces. Add repos, markdown docs, PDFs, files. Open the Space and chat — Copilot uses the curated context. Spaces persist; you can return to them.
Step-by-Step Tutorial
1. Identify use cases
Multi-repo work, docs+code grounding, onboarding kits, support assistants.2. Compare to @workspace
@workspace = single repo, per-conversation. Spaces = curated, persistent, multi-source.3. Check plan
Spaces require Pro or higher. Free tier doesn't include Spaces.4. Decide
Use Spaces when context needs to persist or spans multiple sources. Use @workspace for one-off single-repo questions.5. Build decision tree
Document for your team when to use each.Real-World Example
A platform team built a Space with: their service's repo, internal architecture docs (markdown), API specs (OpenAPI), and onboarding guide. New hires opened the Space and could ask questions across all sources. Onboarding time dropped from 3 days to 1.
Example Prompts / Commands / Code
Feature @workspace Spaces
-----------------------------------------------------------
Scope Single repo Curated (repos + docs + files)
Persistence Per-conversation Persistent across conversations
Setup None Pre-curated
Plan Pro+ Pro+
Best for One-off repo questions Multi-source, recurring context
Latency First call slow First call per Space slow; then fast
Q: Single repo, one-off question?
A: Use @workspace.
Q: Multiple repos, one-off question?
A: Use @workspace per repo, or attach files manually.
Q: Multiple sources (repos + docs + files), recurring questions?
A: Create a Space.
Q: Onboarding kit for new hires?
A: Create a Space with curated docs + key repos.
Q: Support assistant for a product?
A: Create a Space with product docs + API specs.
Common Mistakes
- Using Spaces for single-repo one-off questions — overkill.
- Not using Spaces for recurring multi-source context — missing the benefit.
- Forgetting Spaces require Pro+.
- Treating Spaces as disposable — they persist, so curate deliberately.
Best Practices
- Use Spaces for multi-source recurring context.
- Use @workspace for single-repo one-off questions.
- Curate Spaces deliberately — they persist.
- Check plan: Spaces require Pro+.
- Build a use-case decision tree for your team.
Troubleshooting
| Problem | How to Fix |
|---|---|
| 'Spaces not available' | Your plan doesn't include Spaces. Upgrade to Pro+ or higher. |
| Space feels slow | Reduce sources. Or split into multiple Spaces by topic. |
Practical Exercise
Your Turn
Identify a recurring multi-source context need in your work. Decide if a Space is the right tool. If yes, plan what sources to include.
Professional Challenge
Build a use-case decision tree for your team. Document when to use @workspace vs Spaces vs CLI vs Chat.
Key Takeaways
- Spaces are scoped context containers (GA Sept 2025).
- Use for multi-source recurring context.
- @workspace for single-repo one-off.
- Require Pro+ plan.
- Curate deliberately — Spaces persist.
Frequently Asked Questions
Are Spaces free?
Can I share a Space?
What's the size limit?
Further Reading
Official References
SEO Metadata
SEO title: Copilot Spaces: What They Are and When to Use Them
Meta description: Spaces as scoped context containers — GA September 2025.
Primary keyword: copilot spaces
Secondary keywords: copilot spaces: what they are and when to use them
Search intent: Informational
URL slug: /copilot-spaces-what-when-to-use
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Intermediate, Spaces, Copilot Spaces, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Copilot Spaces: What They Are and When to Use Them
Comments
Comments
Post a Comment