macOS: certain keybindings with cmd key don't work anymore (regression)

[dagi3d]

Issue Description

I downloaded the latest nightly build to give it a try and in principle everything was working fine to me except some keybindings associated to the cmd key that don't work anymore. Other combinations with cmd seem to work as usual.
To reproduce the issue, I added the following keybind:

keybind = cmd+[=text:hi
keybind = cmd+]=text:hi

in version 1.1.3 it sends the text hi. In the tip version(as of 1.1.4-main+e71c23802) it does not do anything

Expected Behavior

Typing cmd+[ or cmd+] should print the text "hi"

Actual Behavior

It does not send any text.

Reproduction Steps

1. Download latest tip release
2. Move to Applications folder to ensure ~/.config/ghostty/config is loaded
3. Include the config added in the "Minimal Ghostty Configuration" section.
4. Open Ghostty
5. Type cmd+[ or cmd+]

Ghostty Logs

No response

Ghostty Version

Ghostty 1.1.4-main+e71c23802

Version
  - version: 1.1.4-main+e71c23802
  - channel: tip
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.none
  - font engine   : font.main.Backend.coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

macOS 15.6

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

keybind = cmd+[=text:hi
keybind = cmd+]=text:hi

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

You must use bracket_left and bracket_right: #7320

We'll document this when 1.2 is released. The motivation is in the PR.

[dagi3d]

thanks a lot @mitchellh, changing the bindings as suggested made it work again.