Restored v12.3.3 fixes minus bearer auth
v12.3.3 shipped 25 bug fixes under "Issue Blowout 2026" but also introduced bearer-token auth that broke SessionStart context injection for everyone. v12.3.4 rolled everything back to v12.3.2 to unblock users.
v12.3.5 restores all 25 fixes, with the bearer-auth mechanism surgically removed.
Kept hardening from v12.3.3
- 5 MB JSON body limit
- In-memory rate limiter (300 req/min/IP)
- Path traversal protection on
watch.context.path RestartGuard(time-windowed restart counter)- Idle session eviction on pool slot allocation
- WAL checkpoint +
journal_size_limit - Periodic
clearFailed()for pending_messages - FTS5 keyword-search fallback when ChromaDB is unavailable
ResponseProcessormarks non-XML responses as failed (with retry) instead of confirming/healthreportsactiveSessions- Summarize hook wraps
workerHttpRequestin try/catch (no more blocking exit code 2) - UserPromptSubmit session-init waits for worker health on Linux/WSL
- MCP loopback self-check uses
process.execPathinstead of barenode - Nounset-safe
TTY_ARGSindocker/claude-mem/run.sh
Removed from v12.3.3
src/shared/auth-token.ts(deleted)requireAuthmiddleware and its wiring inServer.ts/Middleware.tsAuthorization: Bearerinjection inworker-utils.ts(hook client),ViewerRoutes.ts(browser token injection), viewerauthFetch, and the OpenCode plugin
Upgrade notes
~/.claude-mem/worker-auth-tokenfrom a previous 12.3.3 install is harmless and can be deleted.- If your Claude Code session kept the 12.3.3 daemon alive, restart Claude Code once so the fresh 12.3.5 daemon takes over.