I use Claude code for 8-12 hours every day and this is the first time I’ve ever seen this behavior (which is super cool). I have a fable session and an opus session working on the same project simultaneously. While waiting on the opus session to finish with its punch list, I asked the fable session if it could implement its work of if we should wait for the other session to finish.
I then go check the status on the opus session and see this:
The fable session messaged the opus session (directly in the opus session) to coordinate and even told the opus session to ping it when finished so it could move forward. And the crazy part - it apologized to the other session for stepping on its uncommitted changes.
Then I go back to the fable session:
And what’s more crazy is that they’re both interacting with my homegrown session management system and even referring to each other by their normalized session ID within my session management system.
![]()



