Replies: 52 comments 30 replies
-
|
I dont think this is JetBrains specific. You'll see the same behaviour if you open codex via the MacOS Terminal app. The shortcut for a new line is ctrl-j. I would love a way to change this because the muscle memory is strong. |
Beta Was this translation helpful? Give feedback.
-
|
Especially when you bounce between gui chat and codex cli 😂 |
Beta Was this translation helpful? Give feedback.
-
|
same! |
Beta Was this translation helpful? Give feedback.
-
|
wow it works! thanks so much! |
Beta Was this translation helpful? Give feedback.
-
|
Same here! :) |
Beta Was this translation helpful? Give feedback.
-
|
Running Claude Code and Codex side by side. Ctrl+J feels impossible. Configurability would be awesome. |
Beta Was this translation helpful? Give feedback.
-
|
Yea Ctrl+J is a wild design choice. Makes codex fundamentally unusable right now. |
Beta Was this translation helpful? Give feedback.
-
|
Running codex inside tmux in Wezterm on Mac. Shift+Enter runs the command. Ctrl+J is my tmux prefix 🤦 |
Beta Was this translation helpful? Give feedback.
-
|
Ctrl-j is part of my tmux pane navigation and vim splits navigation (replacing [prefix]+j and C-w+j respectively). Having it for a newline is such a strange choice. |
Beta Was this translation helpful? Give feedback.
-
|
Try adding this keybinding to I haven't run into any conflicts or issues with my setup. 🤷 |
Beta Was this translation helpful? Give feedback.
-
|
damn i found out its control + J today. |
Beta Was this translation helpful? Give feedback.
-
|
Really hoping this gets updated, I keep on accidentally submitting half-baked thoughts due to my shift+enter muscle memory. |
Beta Was this translation helpful? Give feedback.
-
|
Please make it Shift + Enter, or configurable. Like everyone else here, I keep submitting half-baked messages which drives me insane. Don't fight our collective muscle memory; ctrl-j is a terrible choice IMHO. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed on it being a wild design decision. But if you are on WSL, here is a workaround that works for me. (And there are probably similar techniques for other terminals).
So a minimal settings.json could look like: |
Beta Was this translation helpful? Give feedback.
-
|
Same, love Codex, especially after new updates, but Ctrl + J feels like learning to play Piano. Please make it adjustable! Or change to Shift - Enter |
Beta Was this translation helpful? Give feedback.
-
|
Definitely change to Shift + Enter. |
Beta Was this translation helpful? Give feedback.
-
|
You can do this with Alt + Enter (on linux at least) |
Beta Was this translation helpful? Give feedback.
-
|
I was using this keybinding successfully until recently. I think they got rid of it. |
Beta Was this translation helpful? Give feedback.
-
|
In CLI 0.128.0 we introduced |
Beta Was this translation helpful? Give feedback.
-
|
Funny that in /keymap shift+enter is there, but doesn't work. Might want to fix that one too. Also, still broken in alpha.2. |
Beta Was this translation helpful? Give feedback.
-
|
Same here, macos arm M2, ghostty. |
Beta Was this translation helpful? Give feedback.
-
|
You can add a new line with Alt + Enter (on linux at least) |
Beta Was this translation helpful? Give feedback.
-
|
I tried this one too, but in Windows Terminal that's the keybinding to toggle between windowed and full screen. I'm not sure if there's an override. I realized my problem was my tmux keybindings. I have Ctrl + vim movements (h j k l) for changing panes in tmux and vim, so Ctrl-j is 'next pane down'. The terminal and/or tmux was converting my Ctrl-Enter and Shift-Enter attempts INTO a Ctrl-j, because it is ALSO the ASCII keycode for a newline. Which is why Ctrl-j is used here -- it's not some novel weird keybinding choice, it's actually just ASCII. So for now I'm trying to find the best way to remove the Ctrl-j binding in tmux in panes that are running codex. It's not great though because the codex process is just node, and I run a lot of stuff with node, so my binding is off in a lot of panes now. I still need to work that one out. But anway. This is the 'why'. |
Beta Was this translation helpful? Give feedback.
-
|
thanks, it is working on ubuntu wsl. |
Beta Was this translation helpful? Give feedback.
-
|
this is unbelievably stupid!! |
Beta Was this translation helpful? Give feedback.
-
|
I've been following this issue for three versions, but it still hasn't been fixed as of v0.47.0. Apparently, they consider it a feature rather than a bug. |
Beta Was this translation helpful? Give feedback.
-
|
What is status on this issue? |
Beta Was this translation helpful? Give feedback.
-
|
Was wondering about this too, im on a Mac - cant go to next line....should be configurable for us. or at least give us a shortcut. |
Beta Was this translation helpful? Give feedback.
-
|
The shortcut for a new line is ctrl-j. |
Beta Was this translation helpful? Give feedback.
-
Ah yes CTRL + J works for mac, thank you sir. |
Beta Was this translation helpful? Give feedback.
-
|
The funny thing: you can solve this by having Claude Code installed, then in the terminal where you want to set up the keybinding for Shift + Enter, just run |
Beta Was this translation helpful? Give feedback.
-
|
🙏🏻 Nicely figured out. Worked for me on MacOS/Wezterm/tmux: -- wezterm config
{
key = "Enter",
mods = "SHIFT",
action = action.SendString("\x1b\r"),
} |
Beta Was this translation helpful? Give feedback.
-
|
Coooooool, thank! |
Beta Was this translation helpful? Give feedback.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as duplicate.
This comment was marked as duplicate.
-
|
for temp work around, thats least annoying w/o installing anything, I am mapping shift+down-arrow to |
Beta Was this translation helpful? Give feedback.
-
|
I wasn't sure if I should post this here. Sorry if I'm wrong. I use the Codex extension in VS Code, but I'm really tired of sending chat messages. I'm a Japanese-speaking developer and always use an IME (Input Method Editor) for keyboard typing. The following explanation is for those unfamiliar with IMEs, so it's a bit lengthy: An IME has a kind of buffer called an "intermediate editing state." Within this buffer, I temporarily edit alphabetically typed characters, convert them to Japanese, and finally input the Japanese text into the actual application. This happens outside VS Code, supported by IME editing features like This behavior frequently causes unfinished Japanese text to be accidentally sent to Codex upon pressing Complicating this further is that the Codex extension's current behavior requires only When using an IME, we must constantly keep track of these combinations in our heads and instantly switch between Therefore, I'd like to request an option in VS Code to always send dialogs only with I realize this could be inconvenient for those not using an IME, so it would be good if it were configurable. |
Beta Was this translation helpful? Give feedback.
-
|
@kekyo, thanks for the suggestion. Could you please open a feature request in the issue tracker? We generally prioritize features based on community member upvotes on feature requests. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
See #3024 (reply in thread) for why Ctrl+J |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
How to do it when running codex in tmux in alacritty on a macbook? |
Beta Was this translation helpful? Give feedback.
-
|
This worked in wezterm, I'm sure you can figure out a similar keybinding in alacritty |
Beta Was this translation helpful? Give feedback.
-
|
• Yes. Codex CLI supports this in config. Add this to ~/.codex/config.toml: [terminal] That makes Ctrl+M insert a newline instead of Ctrl+J. |
Beta Was this translation helpful? Give feedback.
-
|
oh thanks man, I cannot believe we have to set it up manually. Just proves that devs who vibe code these tools do not use these tools themselves. |
Beta Was this translation helpful? Give feedback.
-
|
for those who are using vscode variant IDE. i found this works ps: i got this by querying codex, which is sweet |
Beta Was this translation helpful? Give feedback.
-
|
for anyone who uses Karabiner + iterm2, this works for me. |
Beta Was this translation helpful? Give feedback.
-
|
Actually, use /keymap in Codex CLI to rebind, worked for me. |
Beta Was this translation helpful? Give feedback.
-
|
For the people lurking over here, if you're using Ghostty, this worked for me: Edit config, reload, you're done. |
Beta Was this translation helpful? Give feedback.
-
in
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm encountering a keybinding issue within the IntelliJ integrated terminal, specifically when I'm using an interactive CLI tool like codex.
My goal is to input a multi-line command. In many other terminal applications, pressing Shift + Enter inserts a newline, allowing me to continue writing the command on the next line.
However, when I press Shift + Enter inside the IntelliJ terminal, it behaves exactly like pressing Enter on its own—it immediately executes the current line as a command.
This makes it very difficult to work with multi-line inputs in tools that require them.
I've already looked through the Settings > Keymap to see if Shift + Enter is bound to a conflicting action, but I couldn't find anything obvious that targets the terminal specifically.
Has anyone else faced this issue? Is there a specific setting in IntelliJ's terminal configuration or a keymap override that I can apply to make Shift + Enter function as a simple newline character?
Any help or guidance would be greatly appreciated. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions