Describe the request
Problem
When using a light color theme for the workbench but a dark integrated terminal (common for readability and contrast), the Terminal Cmd+K bar (“Generate Terminal Command”, natural-language command input) often ends up with unreadable text (e.g. dark-on-dark or very low contrast).
What works today
Setting workbench.colorCustomizations → input.foreground (e.g. to a light color) can fix the Terminal Cmd+K field, but it applies to all input controls across the IDE. That makes normal light-theme inputs (search, settings fields, etc.) illegible, so it’s not a viable fix.
What does not help
VS Code–style keys such as inlineChat.background / inlineChatInput.background appear to have no effect on Terminal Cmd+K, likely because that UI is Cursor’s Cmd‑K / prompt-bar flow (terminal-cmd-k), not the VS Code terminal inline chat widget.
Request
Expose one or more workbench.colorCustomizations entries (or Cursor settings) scoped specifically to the Terminal Cmd+K prompt, for example:
cursor.terminalCmdK.inputForeground / inputBackground / placeholderForeground, or
equivalent tokens under workbench.colorCustomizations that only affect that surface.
Why it matters
Users shouldn’t have to choose between readable Terminal Cmd+K and readable global inputs, or resort to custom CSS hacks that break on updates.
Environment (example)
Light workbench theme + dark terminal + default terminal colors; issue reproduced when focusing Terminal Cmd+K and typing in the generate-command field.