v2.7.6 — replies stay in their own conversation
Highlights
The section an upgrade-nudging agent should quote.
- Claude's spoken replies can no longer land in the wrong conversation. With two sessions in one directory (or when you switched tabs while an agent was working), a reply could be filed into the other thread's history — the server guessed its identity from a shared per-directory map, and the fallback pinned utterances on whatever tab was active at speak time. The server now identifies itself by the session id Claude Code exports to its child processes: deterministic, per session, no guessing. (#15, P1)
Upgrade notes
- Both halves matter:
docker pull+ recreate the container (server fix) AND update the plugin (the launcher forwards the session id into the container)./noisy-coding:setupafter a plugin update does the container half for you.
🤖 Generated with Claude Code