{"version":"2.1.247","anchor":"design-login-errors-explain-how-headless-runs-inherit-author","canonical_anchor":"design-login-errors-explain-how-headless-runs-inherit-author","heading":"Design login errors explain how headless runs inherit authorization","tier":"use","area":"Design","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/design-login-errors-explain-how-headless-runs-inherit-author","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Design login errors explain how headless runs inherit authorization\n\nDesign errors now explain that logging in once interactively lets headless and SDK runs reuse it.\n\n**What**\n\nDesign errors now tell you that running `\/design login` once from an interactive session on the same machine lets headless and SDK runs reuse that authorization, instead of only reporting that the command is unavailable.\n\n**Details**\n\n- Applies to both the design sync path and the Claude Design tool.\n- The interactive-session message no longer offers logging in with a Claude subscription as an alternative.\n\n**Evidence**\n\n`non-interactive runs here then reuse that authorization`\n\n- Area: Design\n- Names: `\/design login`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}