runtime: cap MCP responses and isolate stdio sessions#107
Draft
maxkle1nz wants to merge 1 commit into
Draft
Conversation
Large audit/search payloads could exceed what MCP clients can safely persist in chat transcripts, and repeated stdio clients could collide when sharing one runtime root. This adds a transport-level response cap, removes the full audit JSON report from markdown responses, filters m1nd runtime artifacts from ingest/search paths, and documents a session-isolated stdio wrapper. Constraint: stdio clients may be short-lived and concurrent, so the fix must work without requiring a persistent daemon. Confidence: high Scope-risk: moderate Tested: bash -n scripts/macos/m1nd-stdio-session.sh; cargo test -p m1nd-mcp -p m1nd-ingest; two wrapper health probes in parallel Not-tested: persistent HTTP deployment with the new response cap
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
1 participant
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:
Why it matters:
Large audit/search payloads can overload MCP clients and chat transcripts. Concurrent stdio clients can also collide when they share one persisted runtime root.
Verification:
Known limits:
Persistent HTTP deployment was not separately smoke-tested with the new response cap.