I just started exploring this stuff with herdr, it's pretty cool! But I prefer my multiplexer having this functionality built in, as it lets me also have the agent organize my panes and tabs automatically based on what it is working on

I built something similar for my team. I can share context between my own sessions as well as theirs. It's especially useful when debugging problems, so my context can benefit from theirs and vice versa.

Tried to have Claude demo this to me in the standalone Mac OS app. It didn't even know what I was talking about. Then I realized maybe it's only in CC. So I go over to CC and ask it to demo this functionality and it wants to demo via subagents. I correct it that I want separate chats to message each other. It tells me I need to open another Claude session in another terminal of course and just leave it sitting there. So I do that and it has me copy a message to the new conversation, it needed to like name itself or something internally.

It worked, but clunky. Way clunky compared to codex.

I asked cc the best pattern for this in a frontend + backend project just days ago and it suggested mcp server on backend

In fact, I don't understand what is this feature‘s difference between CMUX & Orca?

Oh, they just re-invented `tmux send keys` that I've been using.

Thank God! Was a major pain in the neck.

Curious, Windows is not supported by this.

I've used this feature and saw some weird messages:

> hold swarm, I prepare safe exfil