Introducing cmux history:
cmux now has support for reopening closed terminals/browsers/workspaces via ⌘+Shift+T
History also supports reopening closed Claude Code/Codex/OpenCode/etc sessions
You can also jump back and forward through recently focused workspaces/terminals with the navigation buttons or ⌘+[ and ⌘+] (similar to a browser)
Run `cmux hooks setup` once
Out in 0.64.11
This is my current stack:
Terminal: cmux
Coding model: GPT-5.5(codex)
Open source model: Deepseek V4 Pro(Max)
Harness for open source models: Droid
Terminal editor: Fresh editor
What's your pick?
@shadcn I rotate between Ghostty and Cmux (based on Ghostty)
I think you'd like Cmux a lot. Both perform great and I don't think there's much reason to stay on iterm nowadays
first impressions switching from codex app / claude desktop to cmux:
> the tab management is phenomenal
> low resource usage (swift)
> can import browser settings and use emails, x, and order stuff from amazon all within one app
> finally got claude and codex computer use figured out so now i have clickers running from one app
> cmux.json makes a lot of sense (unified settings file)
> tabs re-open in the best way you could ask for, although i would want support for restoring my sessions, even if it means clicking ctrl+c in the terminals, copying the --resume text in some state file and repasting when the app reopens (good for updates or when i have to close and reopen due to cmux permission changes)
> i still get the terminal
> better than pinned + project sidebar in codex app since i get full control over whats in the sidebar (more ui control = better)
> i did like the natural web ui text rendering instead of raw markdown in the claude and codex apps. but i know its hard to get that when codex cli and claude code are designed entirely around the terminal
> very high taste + free
> was hesitant at first as its takes time to learn new things but i think im okay committing to this
Timelapse #146 (16 hrs)
- Recording on new dii osmo action 4
- Built my second pc, flashed cashyOS + windows 11, and installed my favourite games
- Switched to cmux
- Setting up computer use from terminal
- Decided to take time for myself and watched the walking dead and played some valorant. Didn’t want to get addicted like I used to be so I wrapped it up quickly (insta-lock Reyna dopamine)
Codex CLI is superior over the Codex App.
But as we all know there are some limitations.
Until now.
If you aren’t using Cmux your NGMI.
-Browser capabilities
- Easier co-ordination / management
- Performance
You get best of both worlds.
Codex Cli with Codex App UX.
hey all, i recently joined @manaflowai to work with @lawrencecchen and @austinywang on https://t.co/Ada3cvHb5W .
with that, consider me an extra communication channel for cmux 😆
if you're running multiple agents, you need a terminal multiplexer
I currently use CMUX, it's ghostyy's variant of TMUX, a terminal multiplexer that lets you split your terminal into multiple panes and windows, all inside a single session
instead of juggling separate terminal windows or being locked into one native app like Codex or Claude, you get:
> unlimited horizontal and vertical split panes in one window
> multiple tabs you can switch between instantly
> persistent sessions that survive disconnects
> notifications when any agent needs input
> model-agnostic setup, you can run GPT in one pane, Claude in another, local models in a third
I currently work like this:
> One big window with Hermes Orchestrator on the left
> Multiple open specialised agents on the right
> Agent Control Room session at the bottom
all in one view, zero alt-tabbing between apps
keeping full project context visible at all times
when I'm deep in a project and an agent surfaces something that needs attention, I can see it immediately without breaking focus. when one agent finishes and another needs input, the notification pops in-window.
before CMUX I was constantly switching between terminal windows, losing context, forgetting what was running where
the biggest productivity killer for me is context switching between projects.
CMUX doesn't fix that, but it eliminates context switching within a project, which compounds fast when you're running multiple agents.