fix: redirect debug logs to stderr for MCP stdio compatibility #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
[DB],[MCP],[REFLECT], etc. were polluting stdoutconsole.log()calls toconsole.error()so debug messages go to stderrProblem
When starting Claude Desktop with OpenMemory MCP server in stdio mode, users get errors like:
Solution
Changed all tagged console.log calls to console.error in 5 files:
backend/src/ai/mcp.ts- MCP server startup and request loggingbackend/src/core/db.ts- Database/VectorStore initialization logsbackend/src/memory/reflect.ts- Reflection job progress logsbackend/src/migrate.ts- Migration startup logbackend/src/server/index.ts- Server startup, decay, and prune logsTest Plan
console.log("[patterns remain in backend/srcNotes
This PR supersedes #78 which had developed merge conflicts due to upstream changes. Fresh implementation on current main.
🤖 Generated with Claude Code