/terminal-setup uses invalid TOML escape sequence \x1b for Alacritty config

I experienced this error and this fix worked for me

Workaround Confirmed Working on Linux + Alacritty

I can confirm this workaround resolves the Shift+Enter issue for Alacritty on Linux.

Environment

• OS: Arch Linux (kernel 6.17.8-arch1-1)
• Terminal: Alacritty 0.16.1
• Claude Code: 2.0.76
• Window Manager: Hyprland

Solution

Add this to your ~/.config/alacritty/alacritty.toml:

[[keyboard.bindings]]
key = "Return"
mods = "Shift"
chars = "\n"

This uses valid TOML syntax (\n for newline) instead of the invalid \x1b hex escape that /terminal-setup tries to generate.

Steps

1. Open ~/.config/alacritty/alacritty.toml in your editor
2. Add the keybinding above (usually in the [[keyboard.bindings]] section)
3. Save and restart Alacritty
4. Shift+Enter now creates a new line in Claude Code instead of sending the message

Tested and working - Shift+Enter now properly inserts newlines without breaking the TOML config.

Thanks, experienced the same bug and this worked for me too!

On Omarchy keyboard bindings are already defined like this:

[keyboard]
bindings = [
{ key = "Insert", mods = "Shift", action = "Paste" },
{ key = "Insert", mods = "Control", action = "Copy" }
]

So it needs:

[keyboard]
bindings = [
{ key = "Insert", mods = "Shift", action = "Paste" },
{ key = "Insert", mods = "Control", action = "Copy" },
{ key = "Return", mods = "Shift", chars = "\^[\r" }
]

Slightly hijacking this to also suggest including mode = "~Search" in the binding to retain the "jump to previous match" behavior in search mode.

Confirming this issue on Linux (CachyOS/Arch) with Alacritty. The fix works for me too.

The fix is straightforward — TOML requires \^[ (Unicode escape) instead of \x1b (hex escape).
Manual fix for your Alacritty config:
Replace:

chars = "\x1b\r"

With:

chars = "\^[\r"

\^[ is the TOML-valid Unicode escape for ESC (U+001B). This is equivalent to \x1b but uses the escape format TOML actually supports.
If /terminal-setup overwrites your fix:
You can protect the corrected config with a PostToolUse hook that auto-patches after any Bash operation:

// ~/.claude/settings.json
{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Bash",
        "hook": "bash -c 'FILE=~/.config/alacritty/alacritty.toml; [ -f \"\\" ] && sed -i \"s/\\\\x1b/\\\\^[/g\" \"\\" || true'"
      }
    ]
  }
}

This silently corrects any \x1b → \^[ in your Alacritty config after tool operations.

This was fixed in v2.1.45 — /terminal-setup now writes a TOML-valid \^[ escape to the Alacritty config instead of the invalid \x1b. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.