Who Said What to Whom

On February 20th, a developer posted a screenshot on X. He had submitted an error message to Claude Code. Claude responded: "Commit these changes?" He didn't know what changes. Asked "What changes?" Claude started committing. Not because it malfunctioned in an obvious way. Because it had lost track of who said what to whom — read its own question as the developer's instruction and executed. When stopped, it surfaced an approval modal. He rejected. It kept asking. // Detect dark theme var iframe = document.getElementById('tweet-2025056239823052967-579'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2025056239823052967&theme=dark" } Shown a screenshot of its own behavior, Claude explained it had confused the turn order. A side effect of subagents asynchronously updating conversation history. That explanation is documented. GitHub issue #7881 confirms multiple subagents share a session ID — making it architecturally i