What
Remote managed settings are settings an organization sends to Claude Code from a server. When Claude Code sets them up at startup, it now reads signature details as well as the policy and the settings themselves. Previously it did not.
The startup check on plugin flags works as before. In a guarded mode, Claude Code still refuses --plugin-dir, --plugin-dir-no-mcp, --plugin-url and --agents when plugins are also given inline through CLAUDE_CODE_PLUGIN_DIRS.
Why
Checking remote managed settings now takes an extra piece of information about their signature, the mark that shows they are genuine.
--agents
Run Claude Code programmatically modified, high confidence
| [Custom agents](https://code.claude.com/docs/en/sub-agents.md#choose-the-subagent-scope) | `--agents <file-or-json>` |see the edit
--agents
Connect Claude Code to tools via MCP modified, high confidence
* **Not removed**: a server at [user](#user-scope) or [local scope](#local-scope), in [managed MCP](https://code.claude.com/docs/en/managed-mcp.md), from a [claude.ai connector](#use-mcp-servers-from-claude-ai), or supplied by the SDK or […see the edit
--plugin-dir
Draw in the interface with a mod modified, high confidence
In a session started with `--plugin-dir`, a transcript line says so, such as `ui.render (Pane) refused: Text prop "bogusProp" is not allowed; the engine drew its own`. The [debug log](https://code.claude.com/docs/en/plugins/mods/troublesho…see the edit
--plugin-dir
Mods reference modified, high confidence
| [`claude --plugin-dir <directory>`](https://code.claude.com/docs/en/plugins/mods/create#write-a-mod-yourself) | Loads a plugin directory for one session and reloads its hooks module when you save. Repeat the flag to load several. |see the edit
--plugin-dir
Troubleshoot a mod modified, high confidence
* **A session that hot-reloads a plugin directory**: a dim line in the transcript. That's an interactive session you started with `--plugin-dir`, or one where you [enabled hot reloading](https://code.claude.com/docs/en/plugins/mods/create.…see the edit
--plugin-dir
Troubleshoot plugins modified, high confidence
You're developing a plugin and loading it with `--plugin-dir` or installing it from a local marketplace. These entries cover the failures you hit while developing a plugin. For the checks to run after each change, see [Test and debug](http…see the edit
--plugin-dir
How Claude Code uses prompt caching modified, high confidence
* In interactive sessions, when you add or remove a plugin in a [folder of plugins](https://code.claude.com/docs/en/plugins/create.md#load-a-directory-or-archive-for-one-session) you passed with `--plugin-dir`, the change applies right awa…see the edit
--plugin-dir
Manage sessions modified, high confidence
Not every configuration flag from the original launch is restored. If the session depended on `--mcp-config`, `--settings`, `--plugin-dir`, `--fallback-model`, or directories added with `--add-dir`, pass them again when you resume; directo…see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
--agents on Run Claude Code programmatically