Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Introducing cmux Fork cmux Fork Conversation lets you branch Codex/Claude Code/OpenCode/Pi/Hermes... threads to new tabs, new splits, and new workspaces It's pretty useful for exploring multiple directions in parallel, or if you want to have multiple Claudes with the same context work in the same directory (works surprisingly well)... show more

Lawrence Chen

5,877 subscribers

11,304 views • 3 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

16 Comments

Saatvik3 months ago

forking across harnesses would be cool

Lawrence Chen3 months ago

interesting idea i like

SloaneTsui3 months ago

Wow!

solknight3 months ago

forking with the session context right ?

Lawrence Chen3 months ago

yup

Marco D'Alia3 months ago

very cool! is super hard today to fork a current conversation (at least with claude), and I need it all the time. will be possible to extend this with plugins?

Lawrence Chen3 months ago

how would you like to extend? we're gonna add a cli command in next version that lets you identify which claude/codex session id is associated with each terminal, so you could add your own cmd shift p or right click action to dispatch new workspace/run the claude resume/fork command yourself and do customizations there

Marco D'Alia3 months ago

wow that would be perfect I think!

Kris Constable3 months ago

I've built cmux forking into my workflow a month or two ago, I should have submitted a PR (not as feature rich as yours). It's crazy powerful when you have pi manage this functionality in your workflow automation. pi's cmux windows are more intense than mine 😅

tiff ☀️3 months ago

yessss need this for exploring a different thread so i dont mess up the original context of the OG one

Mahesh Rijal3 months ago

This is super handy. Thanks!

RUFY3 months ago

Kindly check your dm

Chris G.3 months ago

conversation forking solves the biggest problem with long agent sessions. you want to try three different approaches but context is expensive. right now I copy-paste system prompts into new tabs like a barbarian. this is the fix

Ivan Pereira3 months ago

I've been doing this with tmux on pi if anyone is interested

Moez Zhioua3 months ago

Nice work, the ability to branch contexts in parallel cuts down on context drift. I’ve seen similar tricks with hooks, but this feels smoother. Keep context isolated, it prevents accidental state bleed

Luke Jackson3 months ago

Excellent! I was doing this manually with hooks 🪝 Thank you!

Related Videos

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

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

Lawrence Chen

15,723 views • 5 months ago

Using managed agents is perfect for running coding agents anywhere in the world. The beauty of this: • You can resume a session from anywhere • You can fork a session into multiple agents • You can run parallel agents • You can reuse environments Here is how you can do this with Claude Code, Codex, OpenCode, or Hermes.

Using managed agents is perfect for running coding agents anywhere in the world. The beauty of this: • You can resume a session from anywhere • You can fork a session into multiple agents • You can run parallel agents • You can reuse environments Here is how you can do this with Claude Code, Codex, OpenCode, or Hermes.

Santiago

15,931 views • 1 month ago

New in v0.40.0 ⋅ /fork Fork new sessions from current context The original stays intact. /resume returns you to the original. Try different directions without breaking your sessions.

New in v0.40.0 ⋅ /fork Fork new sessions from current context The original stays intact. /resume returns you to the original. Try different directions without breaking your sessions.

Command Code

17,597 views • 4 months ago

💡 Small Codex tip: You don't have to be limited to looking at one thread at a time. 🪟 Open multiple full windows in parallel 💬 Use /side to fork a conversation to ask temporary follow ups 🛟 You can also set a hot key for the Codex pop up Window to quickly fire off new tasks

💡 Small Codex tip: You don't have to be limited to looking at one thread at a time. 🪟 Open multiple full windows in parallel 💬 Use /side to fork a conversation to ask temporary follow ups 🛟 You can also set a hot key for the Codex pop up Window to quickly fire off new tasks

dominik kundel

109,368 views • 6 months ago

I made a Codex fork but it lets you play games in the terminal while you wait for it to finish

I made a Codex fork but it lets you play games in the terminal while you wait for it to finish

Matheus

62,065 views • 8 months ago

Introducing cmux SSH: `cmux ssh user@remote` You can now drag images into SSH'd Claude Code sessions, and cmux will automatically upload them via scp. And when you start a dev server on the remote machine, the browser pane in cmux can reach it at localhost:3000 without port forwarding. The workspace kinda becomes the remote machine, so split panes/new tabs automatically open remote shells. Out in the latest version of cmux (0.63).

Introducing cmux SSH: `cmux ssh user@remote` You can now drag images into SSH'd Claude Code sessions, and cmux will automatically upload them via scp. And when you start a dev server on the remote machine, the browser pane in cmux can reach it at localhost:3000 without port forwarding. The workspace kinda becomes the remote machine, so split panes/new tabs automatically open remote shells. Out in the latest version of cmux (0.63).

Lawrence Chen

49,799 views • 7 months ago

Here's the best setup to manage multiple Claude Code and Codex instances at once. It's not claude --worktree, it's not cmux, and it's not even the Codex App 👀

Here's the best setup to manage multiple Claude Code and Codex instances at once. It's not claude --worktree, it's not cmux, and it's not even the Codex App 👀

Ben Holmes

39,994 views • 5 months ago

ICYMI - Claude Code in the Claude Desktop app! Benefits: → Visual session management instead of terminal tabs → Parallel sessions via git worktrees → Run locally or in the cloud → One-click to open in VS Code or CLI Same Claude Code. Better ergonomics.

ICYMI - Claude Code in the Claude Desktop app! Benefits: → Visual session management instead of terminal tabs → Parallel sessions via git worktrees → Run locally or in the cloud → One-click to open in VS Code or CLI Same Claude Code. Better ergonomics.

Ado

172,126 views • 10 months ago

Supacortex is now public and open source. ✨ New: - Multi Chat - Store conversation and access anywhere in Terminal, Claude code, Opencode, Openclaw etc. Link in the comments.

Supacortex is now public and open source. ✨ New: - Multi Chat - Store conversation and access anywhere in Terminal, Claude code, Opencode, Openclaw etc. Link in the comments.

Yogesh

12,972 views • 8 months ago

finally ported my fav Claude Code feature into Pi: `/subtask` a subtask is a fork of your current conversation, it inherits everything you've discussed, works in the background, and sends only its final answer back into the conversation that spawned it. Less context pollution/bloating and you can continue the main conversation as subtasks are running. here's what's packed into the Pi extension: - a live panel under the prompt: ↑↓ to select, enter to watch a fork work in real time, x to stop or dismiss it - steer a running fork mid-task, or resume a finished one without losing its progress - the model can spawn subtasks on its own and keep working while it waits for the result - forks reuse the parent's prompt cache, so they're cheaper than briefing a subagent - every fork's transcript is a real pi session: reopen it any time with `pi --session `

finally ported my fav Claude Code feature into Pi: `/subtask` a subtask is a fork of your current conversation, it inherits everything you've discussed, works in the background, and sends only its final answer back into the conversation that spawned it. Less context pollution/bloating and you can continue the main conversation as subtasks are running. here's what's packed into the Pi extension: - a live panel under the prompt: ↑↓ to select, enter to watch a fork work in real time, x to stop or dismiss it - steer a running fork mid-task, or resume a finished one without losing its progress - the model can spawn subtasks on its own and keep working while it waits for the result - forks reuse the parent's prompt cache, so they're cheaper than briefing a subagent - every fork's transcript is a real pi session: reopen it any time with `pi --session `

Victor M

18,595 views • 2 months ago

Today we're rolling out Projects in Claude Code on desktop and web. A project is one conversation with Claude. It splits the work into threads itself, runs them as parallel cloud sessions, passes context between them, and keeps going when you leave. In beta for select users.

Today we're rolling out Projects in Claude Code on desktop and web. A project is one conversation with Claude. It splits the work into threads itself, runs them as parallel cloud sessions, passes context between them, and keeps going when you leave. In beta for select users.

ClaudeDevs

2,753,210 views • 1 month ago

Every dot in the new header is a piece of the code behind Cardano's ledger. Watch it grow from 2018 to today, hard fork by hard fork. Want to scrub through it yourself?

Every dot in the new header is a piece of the code behind Cardano's ledger. Watch it grow from 2018 to today, hard fork by hard fork. Want to scrub through it yourself?

Cardano

44,046 views • 1 month ago

cmux now restores your Claude Code, Codex, and OpenCode sessions across quits and reboots. Run `cmux hooks setup` once. Requires v0.64.3.

cmux now restores your Claude Code, Codex, and OpenCode sessions across quits and reboots. Run `cmux hooks setup` once. Requires v0.64.3.

Lawrence Chen

55,605 views • 6 months ago

I just killed all browsers. Introducing Serein, with built-in Claude Code, Codex, and Grok agents that can browse the web. Each agent gets its own tabs and cookies, when they reach a password or payment page, they stop and hand the tab back to you. Serein works with modern agent harnesses like Claude Code, Codex, and OpenCode, using your existing subscription. Currently is free on mac, link in the comment 👇

I just killed all browsers. Introducing Serein, with built-in Claude Code, Codex, and Grok agents that can browse the web. Each agent gets its own tabs and cookies, when they reach a password or payment page, they stop and hand the tab back to you. Serein works with modern agent harnesses like Claude Code, Codex, and OpenCode, using your existing subscription. Currently is free on mac, link in the comment 👇

Ziwen

14,688 views • 27 days ago

Introducing Tabs OpenCode Desktop is now built around tabs. Start a new session in a tab, or open an existing session from any of your projects. Open a new tab when you're starting something new, and close it when you're done. Download the latest to get started.

Introducing Tabs OpenCode Desktop is now built around tabs. Start a new session in a tab, or open an existing session from any of your projects. Open a new tab when you're starting something new, and close it when you're done. Download the latest to get started.

OpenCode

627,706 views • 3 months ago

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted to know when my agents finish, fail, or need me so i built a tmux sidebar. now re-written in rust with worktree support runs inside your actual terminal. on any OS. - agents status' across all your projects at a glance - forwarded ports per project - live threads across amp, claude code, codex, opencode no electron. no blank panes. no new app. extremely fast and light. open source.

Palani — oss/acc

13,971 views • 4 months ago

Hit your usage limit in Codex/Claude Code mid-task? Orca now lets you resume the exact same session in a different agent harness — one click. Codex ⇄ Claude Code, full context intact🔥

Hit your usage limit in Codex/Claude Code mid-task? Orca now lets you resume the exact same session in a different agent harness — one click. Codex ⇄ Claude Code, full context intact🔥

Orca ADE

55,781 views • 3 months ago

The best workflow for parallel Claude Code & Codex agents 01:08 Three core problems to solve 01:35 Conductor 01:55 Isolated workspaces 02:36 Sharing context 02:42 Building in parallel 03:29 Multiple projects 03:46 Managing PRs 04:27 Codex and Opus 04:50 Multiple repos

The best workflow for parallel Claude Code & Codex agents 01:08 Three core problems to solve 01:35 Conductor 01:55 Isolated workspaces 02:36 Sharing context 02:42 Building in parallel 03:29 Multiple projects 03:46 Managing PRs 04:27 Codex and Opus 04:50 Multiple repos

matt palmer

20,131 views • 6 months ago

Nyx is an infinite-canvas IDE where Claude Code, Codex, Gemini, Hermes, and Droid all live on tiles. Arrange them however you want. Watch them all work at the same time. No context switching. Just ten agents running in parallel in front of you.

Nyx is an infinite-canvas IDE where Claude Code, Codex, Gemini, Hermes, and Droid all live on tiles. Arrange them however you want. Watch them all work at the same time. No context switching. Just ten agents running in parallel in front of you.

0xMarioNawfal

49,188 views • 6 months ago

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!

Codex 0.107.0 is here, and with it: FORKS🍴 This minor update includes the ability to fork your current chat history directly with custom multi agents with just a quick prompt. "Fork this session using n subagent(s)" This unlocks some interesting use-cases where you can launch multiple agents that retain all of your chat history up to that point, each in their own independent session. For example, you've been discussing architecture with Codex for 20 minutes, talked through constraints, reviewed existing code, settled on a model. Now you want to see two different implementation strategies side by side. Fork lets both children start from that full shared understanding. With a normal spawn, you'd have to re-explain the entire context to each child, and they'd inevitably miss nuance from the earlier conversation - which is basically a form of compaction/compression. With something like this, you could also just tell it to fork itself 5 times, and implement the same UI/frontend 5 different times in their own worktree to see which one you like the most. Other potential uses: - branching after reviews - try and rollback patterns using worktrees - parallel debugging strategies Otherwise, this is a minor update with improvements to the app server, realtime transcription, and memory. Enjoy!

am.will

42,880 views • 8 months ago