Troubleshoot EchoMemory by surface, not by guesswork
Most support confusion comes from mixing browser setup, MCP setup, and OpenClaw setup into one mental model. Start from the surface where the failure actually occurs.
If cloud features fail everywhere, verify the API key first.
Make sure you copied the full ec_... token without truncation.
Check that the key has the required scopes for the product surface you are configuring.
If an OpenClaw surface works locally but cloud sync fails, separate localhost UI behavior from cloud auth behavior.
Chrome extension issues
If the extension does not appear, confirm it was loaded from the built dist folder.
If the floating icon does not appear on a chat site, confirm the site is one of the supported platforms.
If sign-in succeeds but extension actions fail, the issue is usually backend auth, API access, or site-specific integration rather than extension loading.
If context loading feels incomplete, check whether the content was compressed because it exceeded the long-context threshold.
MCP issues
If Cursor or Windsurf cannot start the MCP server, verify the command, args, and environment variable placement.
If a Claude connector fails in web or Desktop, make sure you are using the remote connector URL flow, not a local stdio config.
If tools are missing, confirm the key has the required MCP scope and that you documented canonical tool names.
If an older client expects alias names, check the compatibility notes before changing the client or docs.
OpenClaw issues
If commands are blocked, check that tools.profile is set to full.
If sync works inconsistently, verify the configured markdown memory directory and whether files are actually inside the expected root.
If the localhost UI opens but cloud features do not, separate local UI behavior from cloud auth behavior when debugging.
If Slack says authorization is required, review OpenClaw channel and user allowlist configuration rather than the Echo plugin first.
Before you ask for help
State which product surface failed: website, Chrome extension, EchoChat iOS app, MCP, or OpenClaw.
State whether you were using the account-backed cloud flow or, for OpenClaw only, the localhost local UI flow.
Include the exact client: Cursor, Windsurf, Claude web, Claude Desktop, or OpenClaw gateway.
Include the exact error message or startup log line.
Include the step where failure occurred, not just the final symptom.