{"version":"2.1.295","anchor":"design-systems-listing-forced-to-http-only-when-aborted-sepa","canonical_anchor":"design-systems-listing-forced-to-http-only-when-aborted-sepa","heading":"Listing design systems uses a different connection setting when stopped separately","tier":"internal","area":"Design Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/design-systems-listing-forced-to-http-only-when-aborted-sepa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Listing design systems uses a different connection setting when stopped separately\n\nWhen the design-systems list request has its own stop signal, Claude Code now asks for an HTTP-only listing\n\n**Unclear.** It is not clear what HTTP-only changes about the lookup or what results it gives.\n\n**What**\n\nClaude Code's design tools can list the available design systems. A design system is a shared set of styles and components. This lookup can be cancelled by a stop signal. When that signal is separate from the one for the rest of the tool's work, Claude Code now marks the lookup as HTTP-only. HTTP is the standard way programs fetch information over the web.\n\n**Why**\n\nThis is a small change in how the design tools fetch their list of design systems, and it only applies in that one case.\n\n- Area: Design Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}