Add --frozen flag to uv run commands in Claude config #1583
+1
−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
When generating Claude Desktop configuration files, the uv run commands now include the --frozen flag. This prevents uv from updating lock files when Claude Desktop launches MCP servers. Without this flag, running MCP servers could inadvertently update uv.lock, potentially causing issues in development environments and CI pipelines. The --frozen flag ensures dependency resolution uses the existing lock file without modifications. This also fixes test_command_execution which was executing uv run without --frozen, causing spurious lock file updates during test runs.
felixweinberger
approved these changes
Nov 6, 2025
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.
This PR adds the
--frozenflag to alluv runcommands generated in Claude Desktop configuration files.Motivation and Context
When Claude Desktop launches MCP servers using the generated configuration, the
uv runcommands were executing without the--frozenflag. This could cause uv to update lock files unexpectedly, leading to:uv.lockduring developmenttest_command_executionran the commandThe
--frozenflag ensures that uv uses the existing lock file without modifications, which is the expected behavior for running applications.How Has This Been Tested?
test_command_executionintests/client/test_config.pyno longer updatesuv.lock["run", "--frozen", "--with", "mcp[cli]", ...]instead of["run", "--with", "mcp[cli]", ...]Breaking Changes
No breaking changes. This only affects the generated Claude Desktop configuration commands. Users who have already configured MCP servers in Claude Desktop may want to regenerate their configuration to get the
--frozenflag, but existing configurations will continue to work.Types of changes
Checklist
Additional context
This aligns with uv's best practices for production deployments where lock file stability is important. The
--frozenflag is already used throughout the repository's own development workflows (in CI, scripts, etc.) and should also be used in generated configurations.