{"version":"2.1.269","anchor":"plugin-runtime-api-gains-a-config-surface-alongside-agent","canonical_anchor":"plugin-runtime-api-gains-a-config-surface-alongside-agent","heading":"Plugin runtime API gains a 'config' surface alongside agent\/fs\/store\/etc.","tier":"soon","area":"Plugin Runtime","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-runtime-api-gains-a-config-surface-alongside-agent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin runtime API gains a 'config' surface alongside agent\/fs\/store\/etc.\n\nPlugin runtime API gains a new 'config' capability alongside turn, tool, agent, fs and others\n\n**Unclear.** The finding does not say what the `config` capability lets a plugin do.\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis gives plugins a dedicated way to interact with configuration, alongside the other capabilities they already had access to.\n\n- Area: Plugin Runtime\n- Names: `config`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5"}