[BUG] `/terminal-setup` with WezTerm assumes that the only possible config is `~/.wezterm.lua` and creates it if the file isn't found.
Resolved 💬 6 comments Opened Oct 17, 2025 by maxim-uvarov Closed Feb 1, 2026
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?
Wezterm looks for configuration files in various locations (see docs). However, /terminal-setup assumes that the configuration file is only in ~/.wezterm.lua. If this file is not found, it creates one with only a keybinding setting for Shift-Enter.
If a user has configs in ~/.config/wezterm/wezterm.lua, they won't be used by Wezterm anymore, since ~/.wezterm.lua takes priority. This caused problems for me and might cause problems for others as well. Please fix this.
What Should Happen?
Claude should understand which config file is in use and modify it.
Error Messages/Logs
Steps to Reproduce
- Have config for wezterm in
~/.config/wezterm/wezterm.lua - Use
/termina-setup - see that the older config isn't used anymore.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.0.21
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗