{"version":"2.1.301","anchor":"agent-proxy-note-becomes-structured-data","canonical_anchor":"agent-proxy-note-becomes-structured-data","heading":"Cloud sessions describe the agent proxy to Claude in a fixed format","tier":"internal","area":"Agent Proxy","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/agent-proxy-note-becomes-structured-data","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Cloud sessions describe the agent proxy to Claude in a fixed format\n\nThe note telling Claude about the agent proxy in cloud sessions is now built from set fields and can say the proxy is no longer active\n\n**What**\n\nIn cloud sessions, Claude Code gives Claude a note about the agent proxy (a go-between that handles network traffic for the session). That note is now built from a fixed set of details instead of being written out directly:\n\n- whether a README is present\n\n- which command-line tools are installed, limited to `aws`, `bq`, `gcloud`, `gh` and `gsutil`\n\n- the certificate bundle at `~\/.ccr\/ca-bundle.crt`\n\nThe same note can also be produced from the session's own environment details. A new message tells Claude: \"The agent proxy announced earlier is not active now.\"\n\n**Why**\n\nThis changes the text Claude sees about its environment in cloud sessions, and lets Claude be told when a proxy it heard about earlier has gone away.\n\n- Area: Agent Proxy\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}