01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Copilot Team Memory in · shared project memory
Copilot Team Memory in Manchester
GitHub Copilot offers custom instructions and repository prompts — useful, but static, size-capped, and per-repo. MemHub adds the dynamic layer: versioned team memory every session can query.
Copilot users feel the same gap as everyone else: yesterday’s debugging breakthrough vanishes before today’s standup. MemHub persists it as structured memory with authorship and search.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/github-copilot-memory
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern
Repository layer owns every database transaction
Source: pull request #214
03
bugfix
Refresh tokens rotate atomically under load
Source: auth/session.ts
Claude Code
Cursor
Windsurf
LOCAL FIT
Why Manchester engineering teams choose MemHub
In Manchester, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.
Every entry carries authorship and version history, which keeps both humans and auditors comfortable.
- Manchester: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
- Local-first writes keep sessions productive through outages and travel.
- One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.
UNIVERSAL COMPATIBILITY
Plugs into any CLI or development tool you use.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.
- Claude Code
- Cursor
- Windsurf
- Cline
- Codex CLI (GPT)
- GitHub Copilot
- Google Antigravity
- Gemini CLI
- Aider
- OpenCode
- CI bots via REST
WHAT YOU GET
Copilot Team Memory in Manchester, without the trade-offs.
01
Governance built-in
Org/project scoping, hashed credentials, and audit trails satisfy security review.
02
Incremental delivery
Sessions receive deltas, keeping prompts lean and attention focused.
03
Self-host option
Keep sensitive repositories’ memory entirely on your infrastructure.
04
Human portal
Leads browse accumulated knowledge without opening an IDE.
05
Beyond instruction files
Dynamic, searchable memory instead of ever-growing static prompt documents.
06
Cross-tool parity
Copilot-era knowledge stays available if the team also runs Claude Code or Cursor.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Status quo | With MemHub |
|---|---|
| Context lives in heads and DMs | Memory is structured, shared, and searchable |
| Every agent re-learns the repo | Sessions open pre-briefed with only what changed |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away |
Connect the tools already in your repository.
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Questions, answered straight.
Does GitHub Copilot support MCP servers?
Copilot’s agent mode increasingly interoperates with MCP tooling; where direct MCP isn’t available yet, teams use MemHub’s REST search and sync APIs or pair it with a companion CLI agent.
How is this better than .github/copilot-instructions.md?
Instruction files are static, per-repo, and size-limited. MemHub is cross-repo, versioned, team-shared, and machine-queried — designed for exactly what those files outgrow.
What happens when our connection drops?
Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again.
Can we try it without sending data anywhere?
Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL.
How much does it cost?
A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited.
MORE LOCATIONS
Copilot Team Memory across EnglandCopilot Team Memory in LondonCopilot Team Memory in EdinburghCopilot Team Memory in San FranciscoCopilot Team Memory in New York CityCopilot Team Memory in AustinCopilot Team Memory in SeattleCopilot Team Memory in BostonCopilot Team Memory in ChicagoCopilot Team Memory in DenverCopilot Team Memory in Los AngelesCopilot Team Memory in Atlanta
EXPLORE OTHER USE CASES
AI Agent Memory
Give every AI coding agent a persistent, team-wide memory.
MCP Memory Server
A hosted MCP memory server your whole team connects to in one command.
Claude Code Memory
Claude Code memory that survives sessions and reaches the whole team.
Cursor Memory
Carry Cursor context across sessions, machines, and teammates.
Codex CLI Memory
Persistent context for Codex CLI — personal today, shared tomorrow.
Cross-Agent Memory
One memory behind Claude Code, Cursor, Codex CLI, and Antigravity.
Developer Knowledge Base
A living knowledge base that writes itself while your team codes.
Self-Hosted AI Memory
Run the entire memory stack on your own PostgreSQL — nothing leaves.
Coding Agent Context
Context engineering for coding agents — brief, don’t dump.
Engineering Decision Log
An ADR habit your team will actually keep — logged by the agents doing the work.
Agent Memory Database
A real database behind agent memory — PostgreSQL, pgvector, row-level security.
Windsurf Memory
Persistent Windsurf context shared with every other agent on the team.
Cline Memory
Give Cline a memory that survives tasks, machines, and teammates.
Antigravity & Gemini Memory
Persistent context for Google Antigravity, Gemini CLI, and the agents around them.
THE NEXT SESSION STARTS HERE