{"version":"2.1.261","anchor":"sdk-session-init-accepts-a-plugins-field-over-stdin","canonical_anchor":"sdk-session-init-accepts-a-plugins-field-over-stdin","heading":"SDK session init accepts a plugins field over stdin","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/sdk-session-init-accepts-a-plugins-field-over-stdin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### SDK session init accepts a `plugins` field over stdin\n\nThe SDK's initialize request can now carry plugin paths over stdin instead of one flag per plugin.\n\nThe SDK's initialize control-request schema now accepts a `plugins` field, mirroring the SDK's `plugins` launch option, so callers can pass plugin-dir entries over stdin instead of adding one `--plugin-dir` flag per plugin. It only takes effect on a CLI launched with `--await-initialize`, where it's read during startup before plugin work happens; a repeated `initialize` call or a remote session transport ignores it. The response's `plugins_applied` field reports whether it actually took effect.\n\n- Area: SDK\n- Names: `plugins_applied`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}