Troubleshooting

Install script returns 404

If curl -fsSL https://agentmemorylabs.com/install.sh | sh or install.ps1 fails with HTTP 404, the CLI CDN artifact may not be published yet.

• Download manually from https://agentmemorylabs.com/downloads/cli/manifest.json and add the binary to your PATH
• See the installation guide for version pinning and manual fallback steps

agent-memory: command not found

Re-open your terminal after install so PATH updates apply.

• macOS/Linux: ensure ~/.local/bin is on your PATH
• Windows: check %LOCALAPPDATA%\Programs\agent-memory\bin
• Verify directly: agent-memory --version

Login and auth failures

If index or search report missing credentials:

• Create an API key at /account
• Set AM_HOSTED_BASE_URL=https://backend.agentmemorylabs.com
• Run agent-memory login --api-key YOUR_KEY or export AM_API_TOKEN

agent-memory doctor failures

Doctor is fail-closed — any fail check blocks indexing until resolved.

• Not initialized: run agent-memory init --managed from the repo root
• Auth: re-run login; confirm API key is active
• Backend unreachable: verify AM_HOSTED_BASE_URL and network access to the control plane
• Use agent-memory doctor --json for machine-readable output

Indexing issues

• Run commands from the repository root where .agentic-memory/config.json exists
• no indexable files found — widen extensions in config or re-run init --managed --extensions .rs,.md,.toml
• Large repos: use index --no-wait then index-watch --job-id <id>

MCP client cannot connect

Hosted MCP uses OAuth over HTTP — not a local serve process.

• Cursor default: https://mcp.agentmemorylabs.com/mcp-full/ (or /mcp for frictionless setup)
• Run agent-memory mcp setup for copy-paste client config
• See MCP Integration for per-client notes