Document mounted server state store isolation in upgrade guide#3236
Document mounted server state store isolation in upgrade guide#3236
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e4c162cf69
ℹ️ 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".
Test Failure AnalysisSummary: The integration test Root Cause: The This failure is not caused by the PR changes (docs-only). It's a pre-existing regression introduced when the dereference middleware was added. Suggested Solution: The dereferencing middleware is re-running expensive schema resolution on every
Option 1 or 2 is the right fix — Detailed AnalysisFailure trace: Timing from stdout: The parsing itself was within limits — the timeout happens entirely inside Why Files involved:
Related Files
🤖 Generated with Claude Code |
Mounted servers in v3 each have their own state store, which means serializable state set by parent middleware isn't visible to mounted tools by default. This was an implicit behavior change from v2 where everything ran in one server context.
Adds a note to the upgrade guide (both the LLM prompt and the human-readable section) explaining the behavior and the workaround:
Non-serializable state (
serializable=False) is request-scoped and automatically shared across mount boundaries, so no workaround is needed there.Closes #3230