{"version":"2.1.285","anchor":"custom-endpoint-name-in-a-message-and-new-headlessartifact","canonical_anchor":"custom-endpoint-name-in-a-message-and-new-headlessartifact","heading":"Messages can now name the custom API address you are using","tier":"notice","area":"API Errors","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/custom-endpoint-name-in-a-message-and-new-headlessartifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Messages can now name the custom API address you are using\n\nWhen Claude Code is pointed at a custom API address, messages can now name its host or say \"a custom endpoint\"\n\n**Unclear.** It is not clear which message shows the endpoint name.\n\n**What**\n\nIf you point Claude Code at a different API server than the default, some messages now name that server's host, or say \"a custom endpoint\" when the host cannot be worked out. Some internal usage data about model consent and runs that did nothing was also added.\n\n**Why**\n\nMessages shown while using a custom API address can say which address is involved.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}