{"version":"2.1.300","anchor":"remote-managed-settings-fetch-supports-an-injected-credentia","canonical_anchor":"remote-managed-settings-fetch-supports-an-injected-credentia","heading":"Managed settings can be fetched with a credential from the launching host","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/remote-managed-settings-fetch-supports-an-injected-credentia","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Managed settings can be fetched with a credential from the launching host\n\nWhen a session is launched by a host, Claude Code can fetch managed settings using a token or API key that host provides\n\n**Unclear.** It is not clear what switches a session into this host-launched mode.\n\n**What**\n\nManaged settings are settings an organization's administrator controls, which Claude Code downloads from a server. In a session started by another program (the host), Claude Code can now fetch these settings with a bearer token or API key that the host hands it.\n\nIn this mode the fetch:\n\n- does not reuse a cached copy check, so it always asks for the settings fresh\n\n- does not go through a proxy\n\n- refuses to follow redirects\n\nIf the host gave no credential, the fetch fails with the message \"No credential from the host that launched this session\". There is also a message for when the settings address moved after the session was launched.\n\n**Why**\n\nThis gives hosted sessions a separate way to sign in for managed settings. If those settings fail to load in such a session, the error now says whether the host supplied a credential.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}