[FEATURE] VSCode extension: per-session settings profiles (--settings parity) and terminal-CLI parity

Use case

Users whose primary surface is the VSCode native extension (not the terminal) cannot launch a session with a chosen settings profile. In the terminal, claude --settings deep-work.json allows e.g. a thrift profile (output-filtering hooks, compression plugins, effort high) vs a deep-work profile (those disabled, effort xhigh). In the extension there is no equivalent — sessions always start from the static settings chain.

Ask

1. A profile selector (or a "start session with settings file…" option) in the extension, equivalent to the CLI's --settings.
2. More broadly: a documented parity story for the extension vs the terminal CLI — several capabilities are terminal-only today and extension-first users discover the gaps by accident.

Related: anthropics/claude-code#90817 (model-conditional configuration) — per-session profiles in the extension would be the manual fallback for that use case.

🤖 Generated with Claude Code