[Bug] VSCode extension terminal setup writes keybindings to DEFAULT PROFILE instead of selected profile

Bug Description
The /terminal-setup command, which enables key bindings for the VS Code integrated terminal when using the VS Code extension in "spawn terminal" mode, writes the Shift+Enter keybinding to the default profile (no profile) rather than to the currently selected profile.
As a result, the keybinding does not take effect when a specific profile is active, yet Claude reports that setup completed successfully. The user is left with no indication of why the keybinding fails to work.
At minimum, the command should inform the user that it only writes to the default profile.
Steps to reproduce

Configure the VS Code extension to use the terminal version.
Launch Claude via the VS Code extension.
Run /keybindings to bind Shift+Enter to newline.
Run /terminal-setup.

Expected vs. actual
Claude reports that setup is complete, but the keybinding does not function because it was written to the default profile instead of the active one. The user has no way to diagnose the failure.

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.1.159
• Feedback ID: cbd7df35-8c9b-4ed5-b3d7-8cd9eaec100d

Errors

[]