Fix long-lived servers mounting volumes as read-only #306
+40
−1
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
Long-lived servers were incorrectly mounting volumes as read-only when the first tool call had the read-only flag set. Since long-lived containers are shared across multiple tool calls, volumes should never be mounted read-only regardless of the first call's read-only status. This change adds a check to skip read-only volume mounting for long-lived servers, ensuring subsequent write operations succeed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
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.
Long-lived servers were incorrectly mounting volumes as read-only when the first tool call had the read-only flag set. Since long-lived containers are shared across multiple tool calls, volumes should never be mounted read-only regardless of the first call's read-only status.
This change adds a check to skip read-only volume mounting for long-lived servers, ensuring subsequent write operations succeed.
Related issue
#305