正在加载视频...
视频加载失败
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
11,166 次观看 • 2 个月前 •via X (Twitter)
16 条评论

forking across harnesses would be cool

interesting idea i like

Wow!

forking with the session context right ?

yup

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?

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

wow that would be perfect I think!

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 😅

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

This is super handy. Thanks!

Kindly check your dm

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

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

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

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

