Unclear The finding does not say what the config capability lets a plugin do.
What
The set of capabilities Claude Code exposes to plugins at runtime (turn, tool, command, agent, fs, store, clock, http, process, settings, env, flag) now also includes a config entry.
Why
This gives plugins a dedicated way to interact with configuration, alongside the other capabilities they already had access to.
Names in the bundleconfig
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Agent SDK reference - TypeScript touched a line naming config after this was published.
| `effort` | `'low' \| 'medium' \| 'high' \| 'xhigh' \| 'max'` | `undefined` | Controls how much effort Claude puts into its response. Works with adaptive thinking to guide thinking depth. See [adjust the effort level](/docs/en/model-confi…agent-sdk/typescript see the edit
Confirmed since
Anthropic's documentation has since written up config, on Troubleshoot Claude Tag setup.
Most of the silence problems in this section span a whole workspace or channel and come down to configuration. If Claude stays silent in one thread but answers everywhere else, a setting isn't the cause. Either Claude's session for that th…claude-tag/admins/troubleshooting see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what the `config` capability lets a plugin do.
Anthropic's documentation agrees
Anthropic's documentation has since written up config, on Troubleshoot Claude Tag setup.