Unclear It is not clear whether the secret-key check is switched on by default or only when turned on remotely.
When Claude sends you a plugin file or a zip archive while helping you build a plugin, Claude Code can now scan the contents first for anything that looks like a secret key, such as a password or access token. This check only runs when a remotely controlled switch is on.
- If it finds possible keys, a "Key check" dialog asks you to choose "Don't send" or "Send it".
- If the check cannot finish, the file is not sent.
A second switch, off unless it is turned on remotely, adds a way for plugins to set their look (colours and backdrop) to the plugin-authoring skill, along with a reference page about it.
It puts a warning in front of sharing a file that may contain a key you did not mean to hand over. The theme option points to plugins being able to change how they look.
tengu_amber_lantern Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.323: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.323. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear whether the secret-key check is switched on by default or only when turned on remotely.
New in this build: tengu_amber_lantern