{"version":"2.1.293","anchor":"desktop-config-egress-model-catalog-and-new-endpoint-fields","canonical_anchor":"desktop-config-egress-model-catalog-and-new-endpoint-fields","heading":"A signed model catalog is now fetched every 5 to 15 minutes","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/desktop-config-egress-model-catalog-and-new-endpoint-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### A signed model catalog is now fetched every 5 to 15 minutes\n\nClaude Code now checks a signed model catalog, the details behind the model picker, every 5 to 15 minutes over the network\n\n**Unclear.** It is not settled whether this catalog check runs in the Claude Code command-line tool or only in the desktop app.\n\n**What**\n\nClaude Code now has a service that downloads a model catalog: signed information used by the model picker, the menu where you choose which Claude model to use. It is checked again every 5 to 15 minutes. Signed means the catalog carries a check that it really came from Anthropic.\n\nThe configuration that controls these outgoing network connections also gained new options:\n\n- Endpoints can now require an exact path and can report undelivered requests as a 503 \"service unavailable\" error.\n\n- The configuration format gained ways to say which conditions a rule applies under and whether sessions run away from your own device.\n\n**Why**\n\nThis is a new regular network connection. If you watch or restrict what Claude Code connects to, expect it to reach out for the model catalog every few minutes.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}