[FEATURE] Customise 'Newline' Behaviour in Terminal

Resolved 💬 2 comments Opened Mar 25, 2026 by ResponsiblyUnranked Closed Mar 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

I use newlines a lot in my prompts with Claude Code, it helps me structure my thoughts and improves readability.

The problem I have is that shift+enter is currently the only way to do that. I am adding far more new lines than I am writing actual prompts, so it would nice if there was an easier way to create a newline character in the terminal window when writing prompts. Especially because if I accidentally hit enter then it submits an incomplete prompt.

Proposed Solution

Allow for a configuration to swap the default newline behaviour. That is, when enabled, this config option would mean pressing the 'enter' key would create a newline and you'd have to press shift+enter in order to actually submit the prompt.

Slack, for example, has this feature when writing messages and I have it enabled for the same reason. It would be great to see this in Claude Code.

Alternative Solutions

To my knowledge, there is no way to customise this behaviour in this way.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

Change the Claude command line tool settings with a flag to enable this option. Perhaps newlineByDefault: true or something.

Then, I can write large prompts with paragraphs in the prompt editor much like I would in a normal text editor.

Then I can press shift+enter to send the prompt.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗