AgentM installs once, for your whole machine. Its customizations go into ~/.claude/ and apply to every project you open, so there is nothing to install per repo and nothing to keep in sync between them. Your memory vault lives in a Google Drive folder, so it follows you across devices.

• A coding agent installed — Claude Code or Antigravity (see requirements).
• A local clone of the agentm repo (this guide assumes it's at ~/agentm).
• Recommended: a Google Drive folder for the vault, so memory syncs across devices (back the vault with Drive).

1. Point the vault at a Google Drive folder. Create a folder named Agent in your Google Drive (the recommended default) and set it as the vault path:

   export MEMORY_ROOT="<your-google-drive>/Agent"

   The install below persists this path into your config, so you only set it once. $MEMORY_ROOT also stays available afterward as a per-invocation override.

2. Install. Run the installer — it takes no target path:

   bash ~/agentm/install.sh

   The customizations land in ~/.claude/, so they apply to every project. The harness hooks install and register themselves as part of this. Re-run the same command any time to refresh.

3. Add the crickets plugins. AgentM pairs with the crickets toolkit — install its plugins for both hosts:

   curl -fsSL https://raw.githubusercontent.com/alexherrero/crickets/main/bootstrap.sh | bash

4. Open a fresh session and run the doctor. Start a new session with your agent so the new config loads, then run the doctor to get a report of how everything's wired up — the vault path, the active backend, the hooks, and anything that needs attention. (For a deeper vault-only pass, see audit the vault.)

Symptom	Fix
The vault path isn't picked up	Make sure MEMORY_ROOT points at the real Drive folder and that it exists. The install persists it; if you set it afterward, re-run the install or set it with agentm_config --vault-path <path>.
You want AgentM in only one project	There is no per-project install any more. AgentM's customizations are machine-wide; what varies per project is its state (PLAN.md, progress.md), which lives in the vault under that project's slug — or in <repo>/.harness/ if you set single-repo state mode.

• Back the vault with Google Drive — set up the Drive-synced vault the recommended install uses.
• Supported configurations — the full matrix of scope, storage, and state-mode choices.
• Update an installed harness — pull a newer version onto your machine.
• Compatibility — supported hosts and the OS matrix.