Remote sessions drop disallowed --mcp-config servers and keep running instead of failing.
What's wrong with this entry?
When policy blocks servers supplied via --mcp-config, a remote session (or a bridge child) now drops just those servers and keeps going. Rejecting the whole run with an error is now limited to non-remote sessions.
- Gated by whether the session is remote (
CLAUDE_CODE_REMOTE) combined with the enterprise MCP policy. - Entries recognized as bridge carrier configs are normalized before being scoped as dynamic.
dropForSideloadPolicy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Feedback dialog drops the "Drafted by Claude" line
Both mention config
-
v2.1.247
Enter in /config acts on the row you are actually on
Both mention config
-
v2.1.248
Project settings can no longer redirect your config directory
Both mention config