[BUG] Install script breaks Alacritty config

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

I installed claude code, and it created a new file with the following contents:

$ cat ~/.config/alacritty/alacritty.toml
[[keyboard.bindings]]
key = "Return"
mods = "Shift"
chars = "\^[\r"

However, I already had an alacritty config located at ~/.config/alacritty.toml. Alacritty prioritized the new file, and so it looked like all my settings had been replaced.

Please include a confirm popup for this type of change. I understand the "it just works" idea behind updating configs, but when it doesn't work entirely right (which it never will), I'd like to be able to debug it myself. If I had seen a popup like "Confirming creating file ~/.config/alacritty/alacritty.toml", I would have identified and fixed this in seconds, instead of wasting time debugging it later. The same goes for any sort of editing of my ~/.zshrc, which (thankfully) the installer script didn't do.

What Should Happen?

I should see a confirm popup to modify my config files.

Error Messages/Logs

Steps to Reproduce

Install it with the shellscript, with a ~/.config/alacritty.toml file already. Then, open alacritty, and it'll load default configs with the new return keybind.

Claude Model

None

Is this a regression?

No

Last Working Version

_No response_

Claude Code Version

2.1.77 (Claude Code)

Platform

Anthropic API

Operating System

Linux

Terminal/Shell

Alacritty

Additional Information

_No response_