Docs · Troubleshooting

Troubleshoot local workspace and account access

Most issues come from account entitlement, local connection state, import limits, or optional embedding setup. Project data remains in the local workspace while you resolve account access.

Desktop says sign-in or authorization is required

Check that the account email is verified and the subscription is active. One user can authorize one device. If changing computers, revoke the current device in Account → Devices, then sign in on the new computer. The old installation will need a new authorization.

A JSON or file import is rejected

Check that the selected file is no larger than 50 MB, each conversation record no larger than 5 MB, and the export contains supported text message fields. Split exports above 10,000 conversations. Binary files and unsupported attachments are not indexed.

Semantic search is unavailable

Full-text search does not need Ollama. For semantic search, start a local Ollama service, install an embedding model, and set `AGENTMEMORY_EMBED_MODEL`. AgentMemory accepts only loopback endpoints and does not install models.

Chrome or MCP cannot reach the desktop

Make sure AgentMemory is open and authorized, then reconnect the extension or check the MCP client’s generated config path and environment variable. Both integrations use a local bridge and cannot work while the desktop is closed.

A download link is missing

The account needs verified email and an active paid entitlement, and a release artifact must be registered for that platform. Links expire quickly and can be used once. No installer is currently listed.

Explore AgentMemory