Supported Configurations

Supported configurations

How AgentM can be set up, and where to read more about each choice. The recommended defaults — a user-scope install with a Google Drive vault — suit most setups; this page is the map of the alternatives.

Install scope

Scope	What it does	When to use it
user (recommended)	Installs to ~/.claude/, so AgentM is available in every project on the machine.	Almost always.
project	Installs into <project>/.claude/.	Team dotfiles, or a project that pins its own config — see Use per-project install.

Full flags: Installer CLI. Moving a project install to user scope: Migration tool.

Vault storage & sync

Where the MemoryVault lives and how it reaches your other devices:

Option	Status	Where to read
Google Drive	recommended right now	Back the vault with Google Drive
git	forthcoming (turnkey via vault-git)	vault-git
Device-local (no sync)	supported	Run without a vault

The search index always stays device-local, so it never syncs. Full picture: Compatibility.

State mode

Where harness state (PLAN.md, progress.md, features.json) is written:

• backend (default) — in the vault, through the active storage backend.
• local — in <repo>/.harness/, with no vault dependency. Set it with install.sh --local-state, or flip an existing install with agentm_config.py --state-mode local.

See Single-repo state mode.

Verification hooks

--hooks (recommended) wires typecheck / lint / test to run on Write and Edit. Optional. Details in Installer CLI.

Hosts

Claude Code and Antigravity are both first-class. See Compatibility.