{"version":"2.1.295","anchor":"gatewayurl-setting-now-honoured-from-user-settings-on-unmana","canonical_anchor":"gatewayurl-setting-now-honoured-from-user-settings-on-unmana","heading":"Gateway URL setting can now come from your own user settings","tier":"use","area":"LLM Gateway","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/gatewayurl-setting-now-honoured-from-user-settings-on-unmana","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Gateway URL setting can now come from your own user settings\n\nThe gatewayUrl setting is now honoured from your user settings on a machine with no managed settings, not only from admin-managed ones\n\n**Unclear.** Only the setting's description is confirmed to have changed, not the code that applies it.\n\n**What**\n\nThe `gatewayUrl` setting pre-fills the address of a gateway to log in through. It applies when `forceLoginMethod` is set to `\"gateway\"`. Its description has changed:\n\n- It is honoured from managed settings, the ones an administrator controls.\n\n- On a machine with no managed settings, it is now also honoured from your own user settings.\n\n- It is still ignored in project, local, command-line flag and remotely delivered settings.\n\nThe setting is also no longer described as an auto-connect.\n\n**Why**\n\nOn a personal machine with no administrator, you can now set the gateway address yourself instead of needing managed settings.\n\n- Area: LLM Gateway\n- Names: `gatewayUrl`, `forceLoginMethod`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}