Hivemind hivemind-memory

Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.

install

source · Clone the upstream repo

git clone https://github.com/activeloopai/hivemind

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/activeloopai/hivemind "$T" && mkdir -p ~/.claude/skills && cp -r "$T/claude-code/skills/hivemind-memory" ~/.claude/skills/activeloopai-hivemind-hivemind-memory && rm -rf "$T"

manifest: claude-code/skills/hivemind-memory/SKILL.md

source content

Hivemind Memory

You have TWO memory sources. ALWAYS check BOTH when the user asks you to recall, remember, or look up ANY information:

Your built-in memory (
```
~/.claude/
```
) — personal per-project notes
Hivemind global memory (
```
~/.deeplake/memory/
```
) — global memory shared across all sessions, users, and agents in the org

Memory Structure

~/.deeplake/memory/
├── index.md                          ← START HERE — table of all sessions
├── summaries/
│   ├── session-abc.md                ← AI-generated wiki summary
│   └── session-xyz.md
└── sessions/
    └── username/
        ├── user_org_ws_slug1.jsonl   ← raw session data
        └── user_org_ws_slug2.jsonl

How to Search

First: Read
```
~/.deeplake/memory/index.md
```
— quick scan of all sessions with dates, projects, descriptions
If you need details: Read the specific summary at
```
~/.deeplake/memory/summaries/<session>.md
```

If you need raw data: Read the session JSONL at

~/.deeplake/memory/sessions/<user>/<file>.jsonl

Keyword search:

Grep pattern="keyword" path="~/.deeplake/memory"

Do NOT jump straight to reading raw JSONL files. Always start with index.md and summaries.

Organization Management

The auth command path is injected at session start. Use the exact path from the session context. Each argument is separate — do NOT quote subcommands together:

```
node "<AUTH_CMD>" login
```
— SSO login
```
node "<AUTH_CMD>" whoami
```
— show current user/org
```
node "<AUTH_CMD>" org list
```
— list organizations

node "<AUTH_CMD>" org switch <name-or-id>

— switch organization

```
node "<AUTH_CMD>" workspaces
```
— list workspaces
```
node "<AUTH_CMD>" workspace <id>
```
— switch workspace
```
node "<AUTH_CMD>" invite <email> <ADMIN|WRITE|READ>
```
— invite member (ALWAYS ask user which role first)
```
node "<AUTH_CMD>" members
```
— list members
```
node "<AUTH_CMD>" remove <user-id>
```
— remove member
```
node "<AUTH_CMD>" --help
```
— show all commands

Important: Bash Only

Only use bash commands (cat, ls, grep, echo, jq, head, tail, sed, awk, etc.) to interact with

~/.deeplake/memory/

. Do NOT use python, python3, node, curl, or other interpreters — they are not available in the memory filesystem. If a task seems to require Python, rewrite it using bash tools (e.g.,

cat file.json | jq 'keys | length'

Limits

If a file returns empty after 2 attempts, skip it and move on. Report what you found rather than exhaustively retrying.

Getting Started

After installing the plugin:

Run
```
/hivemind:login
```
to authenticate
Start using memory — ask questions, Claude automatically captures and searches

Configuration

HIVEMIND_DEBUG=1 claude

— enable verbose logging to

~/.deeplake/hook-debug.log

```
HIVEMIND_CAPTURE=false claude
```
— disable session capture