This page maps the ways you can configure AgentM. You can read more about each choice here. The recommended defaults fit most setups. These defaults use a user-scope install with a Google Drive vault.

There is one install location: $AGENTM_INSTALL_PREFIX, defaulting to ~/.claude/. AgentM is available in every project on the machine, and there is nothing to install per repo.

A per-project install (--scope project) existed until it was retired. If you have a populated <project>/.claude/ left over from one, it is inert — nothing reads it. Re-run the installer to get the current machine-wide install, and delete the old directory when you like.

You can find the full flags in Installer CLI.

You choose where the MemoryVault lives. You choose 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. It never syncs. You can see the full picture in Compatibility.

This controls where you write the harness state. Harness state includes PLAN.md, progress.md, and features.json.

• backend (default) — You write to the vault through the active storage backend.
• local — You write to <repo>/.harness/. You have no vault dependency. You set this with install.sh --local-state. You can flip an existing install with agentm_config.py --state-mode local.

You can read more in Single-repo state mode.

--hooks (recommended) installs the PostToolUse verification hook. This hook runs on Write and Edit. The shipped verify.sh template comments out every check. It has no test-running branch at all. It uses typecheck/lint/vet as example checks. You explicitly leave full-suite tests to /review or CI. You customize verify.sh to activate it. This is optional. You can find details in Installer CLI.

You can use Claude Code and Antigravity. They are both fully supported. You can see Compatibility.