memeri

Troubleshooting — something's not working

Status: ✅ Current · Last reviewed: 2026-06-18

Start at the Connect page → Telemetry Health panel. It tells you, per path (MCP / hooks / tunnel), what's live and what isn't.

MCP shows "not connected"

  • Re-check the server URL ({{GATEWAY_URL}}/mcp) and that the Bearer token matches the one on the Connect page.
  • Make any tool call (ask your AI "What's my current focus?") — MCP only flips to Live after the first call.
  • Regenerated your token recently? Every client using the old one must be updated.

The Terminal says "Console offline"

The Terminal needs the local Console daemon (port 4000) running on your machine. The page shows the exact one-line command to start it — run it and the page reconnects on its own.

A cloud AI can't see my files

Cloud AIs (ChatGPT, Claude Web) get MCP tools but not local file / terminal access. Install the Tunnel (see Installing the Tunnel) to add that, or use Claude Code / the in-browser Terminal.

Auto-grounding isn't happening

The SessionStart / context-injection hooks are Claude Code-only. With other clients, just ask at the start of a chat: "Load my Memeri context for my project."

Still stuck?

Grab the full server-side picture and include it when you report the issue:

curl -H "Authorization: Bearer <your-token>" {{PLATFORM_URL}}/api/v2/diagnostics/me | jq .