Skip to content

docs: point API key setup at console.supermemory.ai - #116

Merged
Dhravya merged 1 commit into
mainfrom
d/readme-console-login-url-982f
Sep 1, 2026
Merged

docs: point API key setup at console.supermemory.ai#116
Dhravya merged 1 commit into
mainfrom
d/readme-console-login-url-982f

Conversation

@Dhravya

@Dhravya Dhravya commented Sep 1, 2026

Copy link
Copy Markdown
Member

What

Update the README API-key setup link from app.supermemory.ai to https://console.supermemory.ai, matching where the current login flow actually lives.

Why

QA flagged that the README still tells users to get an API key at app.supermemory.ai, but the 0.1.6 login authenticates through the console. Verified against the source:

  • plugin/.claude-plugin/plugin.json → version 0.1.6
  • plugin/hooks/lib/auth.jsAUTH_BASE_URL defaults to https://console.supermemory.ai/auth/connect
  • plugin/hooks/lib/error-helpers.js → auth/bad-request errors already direct users to https://console.supermemory.ai

app.supermemory.ai in README.md was the only remaining user-facing reference still pointing at the old host; all other domain references (api., mcp., console., supermemory.ai) are already correct.

Change

-Set your API key (get one at [app.supermemory.ai](https://app.supermemory.ai)):
+Set your API key (get one at [console.supermemory.ai](https://console.supermemory.ai)):

Docs-only. Nothing ships until merge + deploy.

Open in Web Open in Cursor 

The 0.1.6 login flow authenticates via console.supermemory.ai
(plugin/hooks/lib/auth.js), but the README still directed users to
app.supermemory.ai to get an API key. Update the link to match where
login actually lives.

Co-authored-by: Dhravya Shah <dhravya@supermemory.com>
@Dhravya
Dhravya marked this pull request as ready for review September 1, 2026 19:35
@Dhravya
Dhravya merged commit e6227ed into main Sep 1, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants