Docs
Getting started
From signing up to your first recalled session: install, sign in, choose a storage mode and check the hooks.
1. Get updates
Agent Memory is opening up gradually, and there is no public download yet. Leave your email in the form on the home page for product news and a note when you can start. The installer comes with that note.
2. Install
macOS
Requires a Mac with Apple Silicon. The DMG is signed with a Developer ID and notarized by Apple.
- Open the DMG and move Agent Memory.app to Applications.
- Open the app. It lives in the menu bar; closing the window keeps it running.
- On first launch it adds its hooks to the existing settings of Claude Code, Codex, Devin CLI and Grok, and keeps what is already there.
- Codex asks you to trust new hooks. Approve it in Codex.
Windows
Windows ships as a self-contained bundle. See Windows for installing, updating and rolling back.
3. Sign in
Sign in from the app. Your browser opens for authentication, and the app shows the cloud as available when it finishes. From the command line:
agent-memory cloud login --base-url https://agent-memory.jp
agent-memory cloud health --base-url https://agent-memory.jp4. Choose where data lives
Open Settings and choose Cloud, Local or Hybrid. Cloud is the default. Storage and embeddings explains each mode.
Then prepare the embedding model. It isn't bundled with the app; it downloads from Hugging Face into the app's own cache the first time. Start it from Settings, or run:
agent-memory model prepare5. Check the hooks
Hooks connect your agents to Agent Memory. Each one can be turned on or off in Settings or with the CLI.
| Hook | Default | What it does |
|---|---|---|
| SessionEnd | On | Tells the app to pick up the session when it ends. |
| UserPromptSubmit | Off | Searches with the first prompt of each session and passes past context to the agent. |
| SessionStart, SubagentStart, SubagentStop | Off | Pass a prompt you saved, where the agent supports it. |
agent-memory hooks status
agent-memory hooks enable user-prompt-submitCheck that it works
agent-memory health --json
agent-memory search --q "webhook retry" --limit 5health should report "status":"ok". If a search returns nothing yet, finish one agent session and try again.