Makes sense, added as issue: https://github.com/manaflow-ai/cmux/issues/205

iTerm2 has vertical tabs too

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

Could you file an issue with more details: https://github.com/manaflow-ai/cmux/issues

Would greatly appreciate it!

Thanks!

Thanks for the feedback! Mitchell Hashimoto is awesome. Have a PR for fixing devtools here: https://github.com/manaflow-ai/cmux/pull/117

> 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.

IMO (re zoom behavior): if you make a new tab, it should add a new tab as normal and stay zoomed in. the tab bar (of the currently zoomed in panel) would still be at the top while zoomed in, and workspaces still appear to the side

if you make a new split (or navigate splits), it would zoom you back out (contract the panel) and just split/navigate the way it normally would

We're working on a tmux/it2 compatibility layer to make this happen!

No built in way to override new-pane actions right now, but `cmux --help` can automate all parts of cmux.

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

I think we should make this easier though, open to suggestions!

zmx solves persistence well, and I like their minimalism (not supporting windows, tabs, or splits). I think it's possible to make a CLI wrapper for zmx that adds notifications though, so you can have some niceties of cmux without switching to a new terminal. Lowkey we might explore this direction as well.

ive been working on glue for zmx+kitty (would do ghostty if it had proper ipc/scripting support). just changed the repo visibility on on gh cwelsys/kmux.

Sorry you likely encountered this issue: https://github.com/manaflow-ai/cmux/issues/103

The latest release (0.57.0) should fix it.

> a cron or hook that runs tmux capture-pane on each agent pane and checks for the idle prompt is enough to know when one needs attention.

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/