Last Wednesday afternoon, I stared at my screen for three seconds
I had Claude on the left rewriting my website copy, and Claude on the right running a data-cleaning script. When I finished the copy and switched back — boom, it had overwritten my freshly written 800 characters. I thought: why don't these two AIs say hi to each other first?
Claude Code shipped a new feature: let two sessions message each other
This week I was scrolling through Claude's official docs and found they'd quietly rolled out "cross-session messaging." Plain English: you open two Claude Code windows, one runs task A, the other runs task B, and when A finishes it can ping B: "I hit an error on my end, hold up over there." Awei, who's in our group doing Xiaohongshu automation, is already using it. He says he used to manually copy error messages and paste them into the other window — now Claude does the relay, saving him at least half his screen-watching time. Another indie dev friend Xiaolu uses it to coordinate her "frontend" and "backend" sessions — when the frontend finishes tweaking the API, it just yells at the backend: "I renamed the fields to camelCase, update your side too."
Replicate cost: pocket change, ten minutes, three clicks
Money: completely free — it's a native Claude Code feature, no extra charge. Technical barrier: if you can use Claude Code, you're good — no code knowledge needed. Just tell it in the chat "send a message to the other session" and it gets it. First step: open Claude Code's settings panel, find the "Sessions" section, check "Allow cross-session messaging," then give your two regular sessions short names (like "copy" and "data") so they know each other. Setup is about ten minutes, and every use after that is zero cost.
Should you try it now? Three scenarios
If you're just starting out, working solo: skip it for now. One session is enough — get your core business running smoothly first, don't burn time on tooling. If you already have 1–2 stable clients and feel the "too many things to juggle, I'm constantly switching windows" pain: I'd say spend half an hour trying it. Pin your two or three recurring tasks as named sessions and you'll see a visible bump in coordination speed. If you're scaling and juggling two or three contractors at once: set it up now. Cross-session messaging automates the verbal handoffs — "frontend done, notify backend," "test found a bug, notify dev" — saving you at least one full-time assistant's salary.