GitHub Copilot adds workspace memory across repositories for team context

Read the original article →

What happened

GitHub added workspace memory to Copilot on July 10, letting teams persist context about coding conventions, architecture decisions and project terminology across repositories in an organization. Memory entries are scoped by team and respect repository permissions.

The feature is available on Copilot Business and Enterprise plans. GitHub said it reduces repeated context-setting in multi-repo organizations.

Why it matters

Copilot previously treated each chat session as stateless, which meant re-explaining project context every time. Persistent memory across repos addresses a common complaint from teams with microservice architectures.

Permission scoping is important because memory could otherwise leak context across teams that should not see each other's conventions.

MintedBrain take

Curate memory entries deliberately rather than letting the model accumulate noise. Review what gets stored periodically, especially after major architecture changes.

References

This article was originally published at GitHub Docs. For the full piece, read the original article.

Discussion

  • Loading…

← Back to News