Repository navigation
Add resilient Streamable HTTP MCP transport - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
/mcpthat proxies the existing AgentMemory engine instead of creating a fallback memory store.dist/http.mjs, document configuration, and cover the protocol with the official MCP SDK client.Why
A Codex process can remain alive after its stdio MCP transport has closed, but that connection cannot be rebuilt inside the same process. A supervised stateless HTTP endpoint gives a forked or newly started client a clean reconnect path while preserving the single shared AgentMemory engine.
Validation
npm run buildnpm test- 141 files, 1,475 tests passednpm pack --dry-run --json --ignore-scripts- includesdist/http.mjsmemory_nextrequest against the live enginememory_nextthrough this endpoint withoutTransport closed