What
MCP servers are outside programs that give Claude Code extra tools. Programs that control Claude Code, such as the SDK or a remote client, can send it requests. Two of these requests now accept a new liveReply option:
mcp_status(which reports the state of each MCP server) took no options before. WithliveReplyset, and when Claude Code is writing through a cloud session, the answer goes only to the clients attached at that moment. It is sent as acontrol_responsemarkedlive_only: trueand is not stored in the session history. On cloud workers this answer includes each server's configuration, such as URLs, headers and OAuth (sign-in) settings. In headless mode, a successfulmcp_statuswithliveReplyis answered through this separate path.mcp_authenticate(which starts signing in to an MCP server) withliveReplyset sends the sign-in URL through a different reply path than the usual final answer.- The remote-session client keeps track of these live-only requests separately from other requests.
The MCP connection check also now treats a new replaced server state as finished, and takes into account whether a request was relayed.
Why
A program can ask for MCP status, which may include server URLs and headers, without that answer being saved in the session history. It can also receive a sign-in link before the sign-in flow completes.
tengu_cloud_session_shell Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.309: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.309. It isn't a statement about your account. What a flag value here can and cannot tell you