docs: Claude Code v2.1.239 - /list-agents shows teammates, cloud session MCP fix, Agent SDK snapshot on reinitialize

[claude-yolo]

Night shift report

WHY THIS MATTERS: v2.1.239 ships three real behavioral changes: /list-agents now includes agent team teammates and shows this session's own name (so agents can be addressed correctly and self-messages are refused cleanly); cloud sessions with disableSideloadFlags no longer block on startup when a server-delivered --mcp-config is present — they drop the flagged MCP servers and start anyway (fixing a cloud session regression); and the Agent SDK's reinitialize() now gets a snapshot of the live agent set immediately, so reconnecting hosts don't have to wait for a membership event. Plus a Windows cross-session messaging note: local messages now travel over named pipes on native Windows, not sockets.

HIGHLIGHTS:

• /list-agents shows teammates + own name (v2.1.239): Before this release, agent team teammates were silently absent from /list-agents output, and Claude couldn't see its own session name. Both are now listed; self-addressed messages are refused with a clear error instead of "agent not found"
• Cloud session disableSideloadFlags fix (v2.1.239): Previously a server-delivered --mcp-config blocked a cloud session from starting when this enterprise flag was set. Now Claude Code drops those MCP servers (keeping in-process type: "sdk" entries) and starts normally
• Agent SDK reinitialize() snapshot: After a repeated initialize control request (e.g. after a transport gap), Claude Code now immediately sends a snapshot of the current live agent set — reconnecting hosts learn what's running without waiting for the next membership change. Requires SDK v0.3.239+
• WSL policy chain now suppresses /etc/claude-code: wslInheritsWindowsSettings now causes WSL to skip reading /etc/claude-code when any Windows policy key (other than wslInheritsWindowsSettings itself) is delivered — tighter isolation for enterprise Windows+WSL environments
• forceRemoteSettingsRefresh scoped to sessions that fetch server-managed settings: Sessions that don't fetch server-managed settings (e.g. non-authenticated) now start without blocking, closing an unnecessary failure mode
• WebFetch gets seeded: false field: New field in artifactRead output signals when a read didn't deliver the full page source. Requires SDK v0.3.239+
• Artifact force publish clarified: On conflict, the failed publish returns the newer content; Claude should merge and re-publish rather than blindly force-overwrite
• Server-managed settings refresh cadence clarified: Docs now say settings are fetched at startup and refreshed hourly (previously described vaguely as "at authentication time")
• Windows named pipe for cross-session messaging: Local cross-session messages on native Windows travel over named pipes, not sockets (macOS/Linux still use sockets)

---

Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning