{"version":"2.1.274","anchor":"global-config-read-errors-now-surface-instead-of-being-silen","canonical_anchor":"global-config-read-errors-now-surface-instead-of-being-silen","heading":"Global config read errors now surface instead of being silently swallowed","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/global-config-read-errors-now-surface-instead-of-being-silen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Global config read errors now surface instead of being silently swallowed\n\nErrors reading the global config file are now shown instead of being silently hidden\n\n**What**\n\nThe function that reads account login information (`oauthAccount`) from Claude Code's global configuration file now throws explicit errors, 'global config not readable through storage' and 'global config not parseable', when something goes wrong. Previously, any error in this process was caught and the function simply returned nothing, without explaining why.\n\n**Why**\n\nSurfacing the actual error makes it much easier to diagnose problems with a corrupted or inaccessible config file, instead of silently behaving as if no account were logged in.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}