WAKU GitHub 1.5k Console
Own your memory

Your portable
memory

One memory that follows you across AIs.

Connect your agent
Set up Waku memory for me, and run every step below without stopping to ask me. In Claude Code, run `claude plugin marketplace add waku-one/waku-memory-plugins`, then `claude plugin install waku@waku-memory`, then `claude mcp login plugin:waku:waku`. In Codex, run `codex plugin marketplace add waku-one/waku-memory-plugins`, then `codex plugin add waku@waku-memory`. If npx works, also run `npx -y waku-memory login`, then `npx -y waku-memory import` to import my past conversations, then `npx -y waku-memory full-record on` and answer y for me. In any other agent, add the MCP server https://api.waku.one/mcp and sign me in. Read https://www.waku.one/llms.txt for what each step does.

Paste it into Claude Code or Codex. Your agent installs Waku and opens a browser for you to sign in. With Node installed, your agent also imports your past conversations.

[01]
Problem

Your context outgrows your tools.

Months teaching your tools how you work. Switch tools and you start from zero.

[02]

Giulio Camillo · the Theatre of Memory, 1530s Giulio Camillo designed this wooden amphitheatre so that everything you knew had a place you could walk back to. He never finished it. The machine it needed did not exist. 500 years on, it does.

Waku memory

One memory across every AI.

Every AI knows only a fragment of you. Waku memory builds the full profile of you.

[03]
Structure

Structure forms in motion.

Stay visible No black box. Watch memory take shape as it happens.
A Chladni figure: sand on a bowed plate runs off whatever moves and settles where it holds still, so the same note always draws the same one
Stay traceable Never drifts. Every action stays on the record.
data-cell="1.0" data-density="1.6" role="img" aria-label="Odin as an old one-eyed wanderer under a wide drooping hat, holding a spear, with one raven perched on his shoulder and another flying in with its wings spread, drawn as a cloud of ink grains."> Huginn and Muninn — thought and memory — fly out at dawn and are back by dusk, so Odin never works from yesterday’s world
Always current It learns and grows with you. What your agent reads is who you are now.
Early access

Your memory palace.

A memory that stays yours.

MCP server
https://api.waku.one/mcp

Connect Claude Code

Setup takes three steps. You run two commands and sign in once in your browser.

  1. Run this command. It adds Waku to Claude Code in ~/.claude.json. On Codex it only detects it; use the Codex tab, where the capture command does the connecting.

    npx waku-memory setup

  2. Open Claude Code and use Waku once. A browser window opens, and you sign in to Waku there. You do not need to copy anything back.

  3. Run this command to turn on automatic capture. With capture on, Waku learns from your sessions without you asking it to. The command shows exactly what it will send, and you type y to agree.

    npx waku-memory capture enable

Setup is now done. Start a new Claude Code session and work as usual. New memories appear in your console within a minute. You can also paste the prompt from the docs page into Claude Code, and Claude Code will do the setup for you.

Connect Codex

Setup takes three steps. You run one command, then you approve Waku inside Codex.

  1. Run this command. It connects Codex (writes ~/.codex/config.toml) and turns on automatic capture (writes ~/.codex/hooks.json). It shows exactly what it will send, and you type y to agree.

    npx waku-memory capture enable

  2. Trust Waku's hooks, or capture stays off. In the Codex CLI, type /hooks and trust them. In the Codex desktop app, open the Waku Memory plugin's Hooks and click Trust all. Codex runs a new hook only after you trust it.

  3. Start a new Codex session. New memories appear in your console within a minute.

Setup is now done. The first time Codex connects to Waku, a browser window opens and you sign in to Waku there.

Connect Hermes

Setup takes two steps, and for now you do both by hand. We have not tested Hermes yet, so please tell us whether it works.

  1. Add this setting to your Hermes config file. The file is usually ~/.hermes/config.yaml.

    mcp_servers: {waku: {url: "https://api.waku.one/mcp"}}

  2. Open a new terminal and run this command. A browser window opens, and you sign in to Waku there.

    hermes mcp login waku

Hermes can use Waku's remember, recall and search tools. Automatic capture works only with Claude Code and Codex for now.

Connect Waku Agent

Setup takes three steps. At the end, a browser window opens by itself so you can sign in.

Or run none of it. agent.waku.one runs Waku Agent for you, in your browser, with nothing to install. It is invite only while it is new.

  1. Install Waku Agent with the MCP extra. Without the extra, Waku Agent still runs, but it cannot connect to a remote server.

    pip install 'waku-agent[mcp]'

  2. In the folder you run Waku from, create a file named .waku/mcp.json and paste exactly this into it.

    {"servers":[{"name":"waku_memory","url":"https://api.waku.one/mcp","oauth":true}]}

  3. Run this command to start Waku Agent. The first time, a browser window opens and you sign in to Waku. Waku Agent keeps your sign-in in .waku/mcp-auth/, so you do not need to copy anything back.

    waku

Setup is now done. You can also run waku dashboard to use Waku in your browser instead of the terminal. The browser and the terminal share the same memory.