https://github.com/egregore-labs/egregore
Shared intelligence layer for organizations
https://github.com/egregore-labs/egregore
ai claude claude-code cli collaboration developer-tools memory multiplayer shared-memory team
Last synced: 17 days ago
JSON representation
Shared intelligence layer for organizations
- Host: GitHub
- URL: https://github.com/egregore-labs/egregore
- Owner: egregore-labs
- License: mit
- Created: 2026-03-24T15:43:17.000Z (2 months ago)
- Default Branch: main
- Last Pushed: 2026-04-24T15:23:08.000Z (about 1 month ago)
- Last Synced: 2026-04-24T17:20:40.494Z (about 1 month ago)
- Topics: ai, claude, claude-code, cli, collaboration, developer-tools, memory, multiplayer, shared-memory, team
- Language: Shell
- Homepage: https://egregore.xyz/
- Size: 4.54 MB
- Stars: 215
- Watchers: 0
- Forks: 9
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
- awesome - egregore-labs/egregore - Shared intelligence layer for organizations (<a name="Shell"></a>Shell)
README
A shared intelligence layer for teams using Claude Code.
Website ·
Community ·
MIT License
---
Egregore is a shared cognition layer for AI-native collaboration. It turns Claude Code into an inhabitable production environment where every session, handoff, and decision accumulates into a living memory owned by your organization.
With use, the deep context that accumulates enables seamless continuity across multi-agent workflows, visibility into organizational patterns and decision-making, and persistence of collective intelligence across people, sessions, and time.
https://github.com/user-attachments/assets/71a690fb-8a4e-4d0b-9a61-e6cdc7595430
## Install
```bash
npx create-egregore@latest --open
```
This walks you through GitHub auth, names your egregore, creates the repos
(instance + shared memory), clones everything locally, and adds a shell
command to your profile.
To join an existing egregore:
```bash
npx create-egregore join
```
(You will need an invitation from the instance owner. See `/invite` below.)
If your org blocks third-party GitHub Apps, there's a gh-CLI install path: see [INSTALL-GH.md](INSTALL-GH.md) or the [docs](https://egregore.xyz/docs/guides/installation).
## Start
Open a new terminal:
```bash
egregore
```
or, if configured:
```bash
```
Memory syncs. Identity resolves. The session picks up the accumulated context
from every session before it.
## Agent-agnostic use
Claude Code is the integrated runtime, but the shared-memory protocol can be
used by other agents too. Any runtime that can run shell commands inside the
checkout can call:
```bash
bin/agent.sh sync
bin/agent.sh activity --for
bin/agent.sh handoff --from --to --topic "" --body ""
bin/agent.sh ask --from --to --topic "" --question ""
```
See [AGENTS.md](AGENTS.md) and [docs/AGENT-PROTOCOL.md](docs/AGENT-PROTOCOL.md).
## The substrate
Three structural pieces. Everything else is built on them.
**`egregore.md`** — The identity document. What the group is, what it values,
how it works. Every session reads it. It evolves with use.
**`memory/`** — Git-based shared knowledge. Handoffs, decisions, patterns,
quests, people. A separate repo, symlinked into the instance. Version-controlled
provenance on everything.
**Slash commands** — Coordination primitives that encode the session protocol.
Hand off context, capture decisions, invite people, save work. Nobody needs
to learn git workflows or remember conventions.
## Commands
| Command | What it does |
|---------|-------------|
| `/handoff` | Structured context for the next session — decisions, trade-offs, open threads |
| `/activity` | What's happening across the team |
| `/invite` | Bring someone into the egregore |
| `/save` | Stage, commit, push, PR — one command |
| `/dashboard` | Your personal status and recent work |
| `/quest` | Start or contribute to an open-ended exploration |
| `/ask` `/harvest` | Route a question to a teammate or the group |
| `/todo` | Personal task tracking |
| `/reflect` | Capture a decision, pattern, or finding |
| `/deep-reflect` | Cross-reference an insight against accumulated knowledge |
## Invite
```
/invite
```
Adds them as a collaborator on your repos. They join with:
```bash
npx create-egregore join
```
New members inherit the full shared context from session one. The egregore
onboards them.
## What runs
Egregore uses [Claude Code hooks](https://docs.anthropic.com/en/docs/claude-code/hooks)
— shell scripts that fire on session events. All source is in `bin/` and
`.claude/hooks/`. Read them directly.
| Hook | What it does |
|------|-------------|
| **SessionStart** | Syncs memory, resolves identity, renders greeting |
| **PreToolUse** | Boundary isolation + branch protection |
| **PostToolUse** | Local activity tracking |
| **WorktreeCreate** | Isolated git worktrees per topic |
| **PreCompact** | Saves context before memory compression |
| **Stop** | Reminds you to save unsaved work |
No background processes. No daemons. No network calls you don't see.
## Telemetry
Anonymous usage data — command names and timestamps only. Never code, file
contents, or conversation. Opt out anytime:
```bash
EGREGORE_NO_TELEMETRY=1 # in your .env
DO_NOT_TRACK=1 # or the standard flag
```
## Egregore Native: Managed hosting (coming soon)
The open-source Egregore was built as a self-hosted, sovereign architecture without dependencies. Egregore's true capabilities, functionalities and scale are greatly enhanced with managed services.
For teams that want the knowledge graph, live notifications, organizational agents, and persistent GUI: native@egregore.xyz.
## Contributing
Egregore is built by its users. If you already run an egregore:
```
/contribute
```
Forks the repo, creates a branch, and opens a PR to `egregore-labs/egregore`
when you're done.
For manual setup, see [CONTRIBUTING.md](CONTRIBUTING.md).
## From the lab
Built by [Egregore Labs](https://egregore.xyz).
Find the others.