Skip to content

Can't add line breaks with Shift+Enter in terminal since 1.8.0 #4008

Closed as duplicate

Description

@pgt2195

Hi ! Adding line breaks in the terminal when prompting Claude doesn't work for me since updating 1.8.0.

Thank's for your work on this projet btw, great tool.

Activity

  1. added a commit that references this issue on May 3, 2026
  2. Kitenite commented on May 3, 2026

    @Kitenite
    Member

    Oh weird this should've been fixed, sorry about that will look

  3. Kitenite commented on May 3, 2026

    @Kitenite
    Member

    Trying to reproduce the issue, are you able to share any specifics such as OS version and keyboard layout (usually US but perhaps we missed something)

  4. pgt2195 commented on May 3, 2026

    @pgt2195
    Author

    I'm on macOS 26.2, MacBook Air M4, on an ISO AZERTY French keyboard. Shift+Enter doesn't work for me, but Cmd+Enter works though, as GH action bot pointed out, but it's less practical. I also found out that clicking on the text doesn't move the cursor when in Claude CLI. I have to use the keyboard to navigate, but this one doesn't really bother me. I can provide more info if needed.

  5. viddo commented on May 4, 2026

    @viddo

    I had same problem this morning… but only on terminal windows that existed before installing new version. If I start new terminal window/tab it works as expected again. Restarting Claude on pre-existing terminal sessions still exhibits the buggy behavior.

    MacOS 26.3.1 (a). Standard U.S. layout.

  6. Kitenite commented on May 6, 2026

    @Kitenite
    Member

    Related reports (cross-referenced during issue triage — same area, may or may not share a root cause):

  7. pstephan1187 commented on May 27, 2026

    @pstephan1187

    I am also having this issue. It's a bit annoying because it works the exact opposite of all my terminals and TUIs. Would love to see this fixed. I'm on M4 Macbook Air MacOS 26.2. Standard US apple magic keyboard. Using Superset 2

  8. Kitenite commented on Jul 11, 2026

    @Kitenite
    Member

    Closing as a duplicate of #5604, the consolidated tracker for stale terminal-input issues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5604 and we'll reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions