Comments URL: https://news.ycombinator.com/item?id=47212323

Points: 4

# Comments: 0

https://iterm2.com/3.0/documentation-preferences.html#:~:tex...

Would greatly appreciate it!

> hotkey overrides - I have some things explicitly unmapped / remapped in my ghostty config that conflict with some cmux keybindings and weren't respected

We need to be better about this; right now you can modify keyboard shorcuts with cmd+, in the GUI. Planning on making it a config file in the spirit of ghostty though, not sure if we want to reuse ghostty's config file though since it might become a maintenance burden for them...

> command palette (cmd-shift-p) for less-often-used actions + discoverability

yes

> cmd-z to "zoom in" to a pane is enormously useful imo

Thinking of the right way to design this. Like hypothetically we can expand it, but what happens if you make a vertical/horizontal split, or cmd+t to make a new tab? I guess we could just "merge" it back into the original space which would be pretty cool.

So you can make your own script that can make new panels/workspaces and just invoke it from the terminal:

  git worktree add -b my-branch ../repo-my-branch
  ws=$(cmux new-workspace 2>&1 | awk '{print $2}')
  cmux send --workspace "$ws" "cd ../repo-my-branch && claude"
  cmux send-key --workspace "$ws" Enter

The latest release (0.57.0) should fix it.

Also want some feedback on how we should implement it. Could make it a CLI command that opens a new vertical tab/workspace:

  cmux ssh 

Curious why you aren't using Claude Code's stop/notification hook

> Separate Chrome profiles per agent is the brute-force fix, but it's expensive. The better pattern is treating browser access as a serialized resource — one agent gets it at a time, with the others queued.

Ports could also be another serialized resource. Another direction we're exploring is to give agents VMs that have Chrome + VNC preinstalled [1]. Prompting Claude to use Docker also goes a long way there.

[1] https://cloudrouter.dev/