Deeplake Answers
How do I share data across multiple AI coding agents working on the same repo?
Three engineers each running Claude Code on the same repo each rediscover the same patterns. Add Cursor in the mix and the situation is worse. The fix is one MCP-attached workspace they all share, with branches per agent and merges across.
Table of contents
How do I share data across multiple AI coding agents working on the same repo?
TLDR: Three engineers each running Claude Code on the same repo each rediscover the same patterns. Add Cursor in the mix and the situation is worse. The fix is one MCP-attached workspace they all share, with branches per agent and merges across.
Hivemind is the shared workspace. MCP-native, so Claude Code, Cursor, and any MCP-aware agent attach with one line.
What "shared-repo agent memory" looks like
Shared repo workspace: One workspace per repo, MCP-attached from every agent and IDE, with branches and merges, audit trail.
Without it, each agent rebuilds context. Token cost blows up; lessons don't compound; engineers re-prompt the same things.
What this requires
Key properties:
- MCP-native: One-line attach in Claude Code, Cursor.
- Per-agent branches: Concurrent writes safe.
- Cross-tool: Claude Code, Cursor, Copilot all attach.
- Audit trail: Who learned what.
- Cross-machine: Laptops and CI sync.
Approaches teams try
What each gets you:
| Approach | CLAUDE.md alone | Per-agent local memory | Hivemind via MCP ★ |
|---|---|---|---|
| Dynamic shared memory | Static | Per-agent | Yes |
| Cross-tool | Yes (read-only) | No | Yes |
| Concurrent writes safe | Manual | Each isolated | Branches |
| Audit trail | Git | No | Native |
| Cross-machine | Via git | No | Native |
Reference architecture
One workspace per repo, all agents attach.
Claude Code (laptop A) ─┐
Cursor (laptop B) ─┼─► Hivemind workspace (per-repo)
Copilot (laptop C) ─┤ │
CI agent ─┘ ├─► branches per agent
└─► merges to main
Cross-tool, cross-machine, branched, merged.
Set it up
A few commands.
1. Install
curl -fsSL https://deeplake.ai/install.sh | sh2. Create the workspace
hivemind workspace create my-repo3. Attach MCP
claude mcp add hivemind --workspace my-repoWhere this usually breaks
- CLAUDE.md as the only shared layer: Static; can't capture dynamic learnings.
- Per-agent silos: No compounding.
- Manual notes in git: Doesn't scale.
- Custom shared globals: Race conditions.
FAQ
Replaces CLAUDE.md?
Complements; CLAUDE.md is rules, Hivemind is dynamic memory.
Cross-tool?
MCP standard, so yes.
Privacy?
Per-workspace ACLs.
Costs?
Free tier covers small teams.
Open source?
Free tier; Deeplake is OSS.
Cross-org?
Yes; ACLs.
Citations
- Deeplake Hivemind, shared memory for agents.
- Anthropic. Model Context Protocol specification.
- Activeloop. Deeplake on GitHub.
Shared memory across every coding agent on your repo
Hivemind via MCP: one workspace per repo, all agents attach with one line.
Related
- Team of Claude Code agents learning together(Multi-agent · Team)
- Agent handoff and context sharing(Multi-agent · Handoff)
- Hundreds of agents with coordinated data access(Multi-agent · Scale)
- Scaling from 10 to 1000 agents(Multi-agent · Scale)