{"version":"2.1.300","anchor":"egress-allowlist-setting-now-covers-chat","canonical_anchor":"egress-allowlist-setting-now-covers-chat","heading":"Allowed outbound hosts setting now describes Chat as well","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/egress-allowlist-setting-now-covers-chat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Allowed outbound hosts setting now describes Chat as well\n\nThe allowed outbound hosts setting now says it covers Chat, including web fetch, alongside Cowork tasks and Code sessions\n\n**Unclear.** It is not clear whether Chat traffic is newly restricted by this list or was already restricted and only now described.\n\n**What**\n\nThe setting that lists which hosts tools may connect to over the network now says it applies to Cowork, Code and Chat. It used to mention only Cowork tasks and Code sessions.\n\nFor Chat, it covers:\n\n- web fetch\n\n- the file-analysis sandbox, but only if that sandbox's network access is opened\n\n**Why**\n\nOnly the description changed here. Administrators reading it will now see Chat listed alongside Cowork and Code.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}