win11 + wsl（Ubunbu） + claude code（2.1.150） + evermem（0.2.0），alway 403

[maston2]

win11 + wsl（Ubunbu） + claude code（2.1.150） + evermem（0.2.0），alway 403：

/evermem:hub

● Bash(node "C:/Users/hp/.claude/plugins/cache/evermem/evermem/0.2.0/server/proxy.js" &)
⎿  (No output)

● Bash(echo "http://localhost:3456/?key=${EVERMEM_API_KEY}")
⎿  http://localhost:3456/?key=33023557-7e4e-482c-XXXX-XXXXXXXXXXXX

● Memory Hub server started. Open this URL to view your memories:

http://localhost:3456/?key=33023557-7e4e-482c-XXXX-XXXXXXXXXXXX
⎿  Stop says: 💾 EverMem: Save failed
USER: FAILED (403)
Request: {
"group_id": "dnyh0479c",
"messages": [
{
"sender_id": "claude-code-user",
"role": "user",
"timestamp": 1779566446875,
"content": "Caveat: The messages below were generated by the user while running local
commands. DO NOT respond to these messages or otherwise consider them in your response unless the user explicitly
asks you to.\n\n/plugin\n
plugin\n \n\nRun
/reload-plugins to apply plugin changes.\n\nCaveat: The messages below
were generated by the user while running local commands. DO NOT respond to these messages or otherwise consider
them in your response unless the user explicitly asks you
to.\n\n/reload-plugins\n
reload-plugins\n \n\nev
ermem:hub\n/evermem:hub\n\nWhen the user runs this
command:\r\n\r\n1. First, start the proxy server in the background using the Bash tool:\r\nbash\r\nnode \"C:/Users/hp/.claude/plugins/cache/evermem/evermem/0.2.0/server/proxy.js\" &\r\n\r\n\r\n2. Then, construct the
Memory Hub URL with the actual API key using Bash:\r\nbash\r\necho \"http://localhost:3456/?key=${EVERMEM_API_KEY}\"\r\n\r\n\r\n3. Share a simple message with the user
like:\r\n"Memory Hub server started. Open this URL to view your memories:\r\n[the URL from step 2]"\r\n\r\nDo NOT
show the bash commands or code blocks to the user. Just run them and share the final URL.\r\n"
}
],
"async_mode": true
}
Response: {
"message": "Forbidden"
}
ASSISTANT: FAILED (403)
Request: {
"group_id": "dnyh0479c",
"messages": [
{
"sender_id": "claude-assistant",
"role": "assistant",
"timestamp": 1779566446900,
"content": "Memory Hub server started. Open this URL to view your
memories:\n\nhttp://localhost:3456/?key=33023557-7e4e-482c-XXXX-XXXXXXXXXXXX"
}
],
"async_mode": true
}
Response: {
"message": "Forbidden"
}

✻ Churned for 13s

───────────────────────────────────────────────

[tulong66]

我本地复现并确认了这个 403 的更具体根因，补充一下，供你们定位：

Root cause

不是端口占用，也不是 API key 失效。

/evermem:hub 会把 http://localhost:3456/?key=... 这样的本地链接直接回显到当前对话；随后 stop hook 会把整轮 transcript 原样发到 EverMem Cloud 保存。Cloud 侧会拒绝包含 localhost URL 的内容，因此 user / assistant 两条 memory save 都返回 403 Forbidden。

我本地做过最小复现：

• 普通文本保存：202 Accepted
• ?key=[REDACTED] 但不带 localhost：可保存
• 只要内容里有 http://localhost:3456/：403 Forbidden

所以触发条件核心是 localhost URL 出现在 transcript 中。

Local patch that fixed it for me

我在 hooks/scripts/store-memories.js 里，在调用 addMemory() 前增加了一层 transcript 文本脱敏，只替换本地地址：

function redactSensitiveUrls(text) {
  if (!text) return text;

  return text.replace(
    /\bhttps?:\/\/(localhost|127\.0\.0\.1|\[::1\])(?::\d+)?(?:\/[^\s"'`]*)?/gi,
    '[LOCAL_URL_REDACTED]'
  );
}

const lastTurn = extractLastTurn(lines);
const lastUser = redactSensitiveUrls(lastTurn.user);
const lastAssistant = redactSensitiveUrls(lastTurn.assistant);

然后继续用脱敏后的 lastUser / lastAssistant 调 addMemory()。

Verification

我本地做了两层验证：

1. 用与 /evermem:hub 同形态的 transcript 直接跑 store-memories.js，修复前稳定 403，修复后变成：
   • 💾 Memory saved (2) [assistant: 60, user: 151]
2. 实际再跑 /evermem:hub，Memory Hub 页面能正常打开并加载 memories，不再触发保存失败。

如果你们愿意，我也可以把这个 patch 整理成 PR 版本。