{
  "id": 14902114,
  "title": "I gave two Claude Code sessions a PM and an engineer job. My job was to watch",
  "url": "https://urgent.news/2026/10/16/i-gave-two-claude-code-sessions-a-pm-and-an-engineer-job-my-job-was",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-16T07:56:57.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/urion/i-gave-two-claude-code-sessions-a-pm-and-an-engineer-job-my-job-was-to-watch-116o"
  },
  "original_language": "en",
  "account": "Claude Code sessions can communicate with each other using a feature called cross-session messaging, introduced in version 2.1.224. This allows two sessions to collaborate on a repository, with one acting as the PM (product manager) and the other as the engineer. The PM writes specs and reviews them, while the engineer implements the specs and sends a message asking for review when finished. The engineer then sends a list of files it modified for the reviewer to examine. The system has two review rounds and stricter rules to prevent endless loops. After fixes, a verification pass ensures the changes work as intended before merging. The PM leaves comments as Reado Markdown files, allowing both sessions to read the same list, and the engineer verifies fixes before merging. This setup allows the PM to scale across multiple projects, and the system has proven effective for the described project, rind-ui, with good results and minimal token usage.",
  "summary": "Since August, Claude Code sessions can talk to each other. The feature is called cross-session messaging and arrived in v2.1.224: a session finds your other sessions with ListAgents and sends one of them a message with SendMessage . What travels is only the text Claude writes for the other session, never the conversation history or files. I've been using it to build rind-ui, a headless UI…",
  "key_points": [
    "Two Claude Code sessions collaborated using cross-session messaging",
    "One session acted as PM, the other as engineer",
    "PM wrote specs, engineer implemented, then sent modified files for review"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}