Local console (#memory) broken on non-localhost hosts: no auth sent + wrong graph endpoint

Author: evgenygurinCreated Sep 17, 2026Updated Sep 17, 2026

Environment

  • Server: self-hosted supermemory-server, version 0.0.8 (latest stable), Linux x64
  • Access: via public HTTPS URL (Railway), i.e. NOT localhost

Problem 1: console never authenticates

The bundled console (local-console.js, lazy-loaded on /#memory) contains zero references to Bearer, apiKey, Authorization or localStorage. Every API call goes out without credentials, so on any non-localhost host everything returns 401. It only works on http://localhost:6767 where the server auto-applies the key for unauthenticated localhost requests. There is no key input in the UI.

Problem 2: memory graph calls a non-existent endpoint

useMemoryData in the bundle does: POST /v3/documents/documents with body {page, limit, sort, order} That route does not exist (verified: 404 even with a valid key). The correct endpoint is POST /v3/documents/list. UI shows: Error loading graph: /v3/documents/documents → 401/404.

Repro

  1. Run supermemory-server 0.0.8, expose it on a public URL.
  2. Open /#memory — graph fails; every data call is unauthenticated.

Expected

  • A key input (persisted, e.g. localStorage) attached as Authorization: Bearer on all calls.
  • Graph uses POST /v3/documents/list.

Source: supermemoryai/supermemory