[vincenzopalazzo]

Summary

• Default openmemory_query (type=contextual) ran hsg_query with no try/catch or timeout. A hung embed, rate-limit throw, or long vector writeback dropped the per-request Streamable HTTP POST (Streamable HTTP error: Error POSTing to endpoint, empty status), so the first query looked like a total outage.
• Wrap HSG and factual search in a 12s timeout (OM_MCP_QUERY_TIMEOUT_MS) and return a normal MCP tool error (isError + readable message) instead of letting the transport die. Unified queries fail-soft on HSG and still return facts.
• Unpatterned factual queries dumped the whole temporal graph (1MB+). Cap them at k (patterned queries still cap at 32). Same fail-soft + cap on the Python MCP path.

Test plan

• npx vitest run tests/mcp_query_failsoft.test.ts (7 tests)
• npm test in packages/openmemory-js (65 tests)
• npm run typecheck
• CI passes
• Default openmemory_query with no type returns a tool result or isError, never a transport drop
• list / get / store / delete / type=factual with fact_pattern still work

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 70a92566a7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[nullure]

Thanks for the detailed root-cause writeup on the Streamable HTTP session drop — that's a sharp diagnosis.

This targets packages/openmemory-js/src/ai/mcp.ts and the HSG query path, which were removed in LongMemory's architecture rewrite. The current MCP transport lives in src/mcp/transports/http.ts with tools in src/mcp/tools/*, and recall now goes through the Hydrograph engine instead of HSG.

Closing as superseded by the rewrite. If a hung/slow recall can still drop the Streamable HTTP session on current main, that's still worth fixing there — please re-file against src/mcp/transports/http.ts / src/core/recall/associative_recall.ts if you can reproduce it.