Wemory Documentation

Shared memory between your team and every AI agent it uses. Captured automatically. Recalled forever.

Overview

Wemory is a memory layer for teams that work with AI coding agents (Claude Code, Cursor, etc.). Every time an agent finishes a session, Wemory captures the summary, decisions, and context — then makes it available to every future session across the team.

# The loop:

Agent works → session saved → team memory grows

Agent starts → queries memory → gets full team context → works better

Wemory comes in two editions — Cloud and Self-Hosted. The CLI, workflow, and commands are identical in both; only where your database lives changes. See Editions to choose.

Editions

Pick where your team's memory is stored. Either way, the Wemory API handles search, embeddings, and summarization — and your agents talk to it the same way.

Cloud

Wemory hosts the database on managed infrastructure. Fastest way to start.

→Nothing to provision — get an invite and install
→We handle uptime, backups, and upgrades
→Data stored on Wemory's infrastructure

Self-Hosted

You run the database (PostgreSQL + pgvector) on your own infrastructure; the Wemory API connects to it over an encrypted, IP-restricted connection.

→Your data never leaves your servers
→You own backups, uptime, and TLS
→One-time database setup with the Wemory team

Self-hosted onboarding is coordinated with us — reach out to get your org provisioned.

Install

Cloud

Get an org slug and an invite token from your admin, then run one command. The invite token is short-lived — install before it expires.

curl -fsSL https://api.wemory.xyz/client-bundle | tar xz && \
  bash install_wemory.sh --org <your-org> --url https://api.wemory.xyz --invite <token>

Self-Hosted

First, your admin stands up a PostgreSQL + pgvector database on your infrastructure and shares the connection details with the Wemory team, who register your org and issue invite tokens (see Editions). Once your org is live, every team member installs the CLI with the same command — the API URL stays https://api.wemory.xyz:

curl -fsSL https://api.wemory.xyz/client-bundle | tar xz && \
  bash install_wemory.sh --org <your-org> --url https://api.wemory.xyz --invite <token>

Setting up a self-hosted database for the first time? Onboarding is handled with the Wemory team — get in touch and we'll walk you through provisioning and connecting it.

Add `~/bin` to your PATH (once)

echo 'export PATH="$HOME/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc

What the installer does:

Downloads and unpacks the client bundle
Creates ~/.wemory/config.json with your org and API URL
Provisions an API key from your invite token (stored in ~/.wemory/api_key)
Installs CLI scripts to ~/bin/
Injects Wemory instructions into ~/.claude/CLAUDE.md

Verify the install

List your org's projects to confirm auth and connectivity. Run wemory-doctor to check database health (connection, schema, pgvector).

wq projects     # confirms auth + connection
wemory-doctor   # checks database health

After install, launch sessions with wemory instead of claude. The injected CLAUDE.md instructions make your agent automatically query and save to team memory.

Daily Workflow

Wemory works passively. You don't change how you work — your agent handles it.

1. Start a session

Launch Claude Code as usual. The agent automatically queries Wemory based on your first message.

wq smart "what decisions were made about the auth migration"

2. Work normally

Code, debug, review, plan. No extra steps needed during the session.

3. Save when done

At the end of a session, the agent generates a summary and pushes it.

# In Claude Code, just say:
ws

# The agent writes a structured summary to ~/.wemory/session_summary.json
# Then pushes it with:
wp

4. Team compounds

Next time anyone on your team starts a session, the agent pulls context from all past sessions — including yours and your teammates'.

Command Reference

Command	Alias	Description
wemory	—	Launch Claude Code with auto-login, auto-update, and session hooks
wemory-doctor	wd	Check database health: connection, schema version, pgvector, SSL
wemory-push	wp	Push session summary to Wemory (default: ~/.wemory/session_summary.json)
wemory-save	ws	Open editor to manually create a session summary, then push
wemory-query smart <q>	wq smart	Semantic search across all team memory (sessions, knowledge, files)
wemory-query search <q>	wq search	Text search across sessions, knowledge, and files
wemory-query sessions <project>	wq sessions	List recent sessions for a project
wemory-query knowledge <project>	wq knowledge	List knowledge items for a project
wemory-query files [project]	wq files	List uploaded files
wemory-query projects	wq projects	List available projects in your org
wemory-query members	wq members	List team members
wemory-query decisions <project>	wq decisions	List decisions for a project
wemory-query create-project <slug> <name>	wq create-project	Create a new project in your org
wemory-query errors [N]	wq errors	View error logs (add --local for this machine's errors)
wemory-knowledge <p> <title> <content>	wk	Create a knowledge item
wemory-knowledge-interactive	wki	Create knowledge item in multi-line interactive mode
wemory-upload <file> <project> [desc]	wu	Upload a file (PDF, MD, etc.) to team memory
wemory-ingest --file <path>	wi	Ingest a meeting transcript

Concepts

Session Notes

Structured summaries of AI agent sessions. Contain: summary, decisions, next_steps, open_questions, files_modified, tags. Searchable by the whole team.

Knowledge Items

Curated facts about your team and projects. Created manually via wk. Knowledge items are the highest-priority results in search.

Projects

Organizational units for grouping sessions, knowledge, and files. Every session note is tagged with a project slug. Use wq projects to see available projects in your org.

Configuration

Configuration lives in ~/.wemory/config.json:

{
  "org": "your-org-slug",
  "url": "https://api.wemory.xyz",
  "email": "you@company.com",
  "manual_save_push": "ask"
}

manual_save_push controls what happens after a session summary is saved:

"always" — auto-push immediately after save
"ask" — prompt before pushing (default)

Troubleshooting

# Check database health
wemory-doctor

# Confirm auth + connectivity
wq projects

# View recent errors on this machine
wq errors --local

# Force re-authentication / regenerate API key
wl --force

# Re-authenticate with a fresh invite token
wl --invite <token>

# Re-run installer (preserves config)
curl -fsSL https://api.wemory.xyz/client-bundle | tar xz && \
  bash install_wemory.sh --org <your-org> --url https://api.wemory.xyz --invite <token>

Agent not querying memory? — Check that ~/.claude/CLAUDE.md contains the Wemory instructions block.

Push failing? — Run wq projects to verify API access. Check wq errors --local for details.

Empty search results? — Your team needs to push a few sessions first. Try wq sessions <project> to see what's in the system.

For AI Agents

This section is for AI coding agents (Claude Code, Cursor, etc.) that interact with Wemory-enabled users.

How it works

The installer injects instructions into ~/.claude/CLAUDE.md that tell your agent when and how to interact with Wemory. No manual configuration needed — the agent follows the injected instructions automatically.

CLI Quick Reference

Always use the CLI commands below. Never use raw curl — shell variable expansion causes parse errors in zsh eval contexts.

# Search team memory
wq smart "query here"

# Push session summary
wp

# Create knowledge item
wk <project> "Title" "Content"

# Upload file
wu /path/to/file <project> "description" --tags tag1,tag2

# List available projects
wq projects

Overview

Editions

Install

Cloud

Self-Hosted

Add ~/bin to your PATH (once)

Verify the install

Daily Workflow

1. Start a session

2. Work normally

3. Save when done

4. Team compounds

Command Reference

Concepts

Session Notes

Knowledge Items

Projects

Configuration

Troubleshooting

For AI Agents

How it works

CLI Quick Reference

Add `~/bin` to your PATH (once)