Cursor IDE, all text inputs (code editor, AI chat, and other input fields)
While composing Japanese text anywhere in the Cursor IDE, the background of the in-progress IME text intermittently turns black. This is not limited to the AI chat input. The same thing happens in the code editor and in other IDE text fields.
The floating candidate window is fine. Committed text is also fine. The black background appears only on the uncommitted composition range, then disappears after the text is committed. It can look normal on the next keystroke and black again after that.
Other Mac apps do not do this. Reinstalling Cursor does not help. Changing the color theme or macOS appearance does not help.
In the AI chat input, the focused element (`.aislash-editor-input`) has an inline `background-color: transparent`. Its parent (`.ai-input-full-input-box`) is opaque (`var(–vscode-input-background)`) and has `contain: paint`. macOS Japanese input takes the composition background from the focused element, so that transparent background is sometimes painted black. The same black composition background also appears in IDE inputs that do not use this element, including the code editor.
Actual Behavior
The composition range background alternates between the normal input color and solid black.
Does this stop you from using Cursor?
No, but Japanese input in the chat box is hard to read while converting.
Steps to Reproduce
Open Cursor on macOS.
Switch to the macOS Japanese input source.
Type Japanese in the code editor and leave the text uncommitted.
Type Japanese in the AI chat input and leave the text uncommitted.
Repeat in another IDE field, such as the command palette or the find box.
Watch the background of the uncommitted text while typing, changing candidates, and moving the caret.
Expected Behavior
The composition range uses the same opaque background as the chat input box.
Thanks for the checks. I tried both, and the black background still appears in every case while Japanese text is uncommitted (not confirmed with Enter).
New Agents Window, before changing any settings
Attachment: before_changing_settings_agent2026-10-16 11.04.05
The black background appears in the Agents window chat box as well, not only in the Editor layout.
After adding “disable-hardware-acceleration”: true and fully quitting/reopening Cursor
Attachment: after_changing_settings_agent2026-10-16 11.18.29
The black background still appears in the Agents window chat box.
Attachment: after_changing_settings_editor2026-10-16 11.26.20
The black background still appears in the Editor layout chat box too.
So disabling hardware acceleration did not change the behavior.
Hey @den_den1, thanks for running both checks and for the recordings, they helped a lot.
Looking through them frame by frame, the text you’re typing (the underlined part) stays on the normal input background the whole time. What turns dark is the conversion candidate panel that pops up above it: it shows black candidate text on a dark gray panel, with a large empty dark area underneath, so the candidates are very hard to read. Is that panel what you mean by the black background?
If so, this looks like a macOS 26 behavior. The new glass-style candidate panel takes on the colors of whatever is behind it, so over a dark editor it turns dark while its text stays black. A few things to try:
Open System Settings → Accessibility → Display and turn on “Reduce transparency”. This makes the panel opaque, which usually makes the candidates readable again.
If your macOS has it, open System Settings → Appearance and set “Liquid Glass” to “Tinted”.
In Cursor, press Cmd+Shift+P, run “Preferences: Open User Settings (JSON)”, add the line “window.systemColorTheme”: “dark”, save, and fully restart Cursor (Cmd+Q). This tells macOS that Cursor’s window is dark, which may make the panel switch to white text.
Could you also check one thing for us: does the same dark panel appear when you type Japanese in another app with a dark background, for example VS Code with a dark theme, or Terminal with a dark profile?
Let us know which of the steps above helps, and what you see in the other app.
Yes, that is exactly the conversion candidate panel. The background of that panel turns black.
I tried all three steps:
System Settings → Accessibility → Display, and turned on “Reduce transparency”.
System Settings → Appearance, and set “Liquid Glass” to “Tinted”.
In Cursor, I added “window.systemColorTheme”: “dark”, saved, and fully quit and restarted Cursor with Cmd+Q.
In every case, the candidate panel background still turned black.
Update: switching macOS to Dark mode is an effective workaround. It does not fix the underlying behavior.
My Mac was in Light mode while Cursor used a dark theme. An AI pointed out that mix as the likely cause. With the macOS 26 Japanese input, the candidate text color follows the macOS appearance (black in Light mode, white in Dark mode). The panel background follows the dark screen behind it. In Light mode I got black text on a dark panel, which was unreadable.
After I set System Settings → Appearance to Dark, the candidate panel background still changes its tint depending on what is behind it, and it is often dark. The candidates now show in white text, so they are easy to read. The dark background no longer hides the candidates, but the panel itself still takes on the color behind it.
I also tested whether the chat input’s inline background-color: transparent was the cause. I locally changed it to var(--vscode-input-background) and fully restarted Cursor, but the panel still turned black with unreadable text, so that style is not the cause. I have reverted that change.
It comes from macOS 26 when the macOS appearance (Light) does not match a dark app theme. Setting macOS to Dark mode makes the candidates readable, but it does not stop the panel background from changing.
One temporary workaround would be for Cursor to default “window.autoDetectColorScheme” to true. It is false by default, so Cursor can stay on a dark theme while macOS is in Light mode. With it set to true, Cursor follows the macOS appearance: Light mode uses a light theme, and Dark mode uses a dark theme. The candidate text color and the theme behind the panel then match, so the candidates stay readable. This does not stop the panel background from changing color. It only avoids the mismatch.
Hey @den_den1, thanks for testing all of those and for tracking down the Light / Dark mismatch.
That matches what we see on our side. macOS draws the conversion candidate panel itself, not Cursor. On macOS 26 the panel’s text color follows the system appearance, while its glass background picks up whatever is behind it. That’s why none of the in-app settings (including “window.systemColorTheme”) or your CSS change affected it.
About your suggestion: new Cursor installs already follow the macOS appearance by default. Installs from before that change, like yours, keep the theme they already had, so nobody’s theme changes unexpectedly after an update.
If you’d like to keep macOS in Light mode, you can turn it on yourself:
Press Cmd+Shift+P and run “Preferences: Open User Settings (JSON)”.
Add the line “window.autoDetectColorScheme”: true and save.
Optionally, choose which themes to use with “workbench.preferredLightColorTheme” and “workbench.preferredDarkColorTheme”.
In the Agents window, open Settings, go to Appearance, and set the theme to System.
Otherwise, keeping macOS in Dark mode as you found keeps the candidates readable while Cursor stays dark.
Updating to macOS 27 resolved this. Even with macOS set to Light mode and Cursor set to a dark theme, the background no longer turns black. Thank you for your help.