Alacritty setup writes invalid TOML escape \x1b instead of \u001b

[TheHalfrican]

Bug

When Claude Code sets up the Shift+Enter keybinding in Alacritty's alacritty.toml, it writes:

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

\x is not a valid TOML escape sequence (TOML spec), which causes a parse error at the chars line and prevents Alacritty from loading the config entirely.

Expected behavior

The installer should use the TOML-compatible Unicode escape \u001b:

chars = "\u001b\r"

Reproduction

1. Have an existing alacritty.toml config
2. Install Claude Code and add it to PATH
3. Alacritty fails to load with a parse error on the chars line

Environment

• OS: Windows 11 Pro (25H2)
• Alacritty: 0.16.1
• Config path: %APPDATA%\alacritty\alacritty.toml

Notes

• The setup correctly creates a .bak backup before modifying the file
• Reinstalling/updating Claude Code re-applies the broken escape, overwriting manual fixes

[github-actions]

Found 3 possible duplicate issues:

1. terminal-setup writes invalid TOML escape sequence in Alacritty config #24714
2. /terminal-setup uses invalid TOML escape sequence \x1b for Alacritty config #14793
3. terminal-setup writes invalid TOML escape sequence for Alacritty config #19288

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code