Claude Code corrupt .credentials.json with non-array scopes hangs CLI on startup

What this error means

corrupt .credentials.json with non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh is a Claude Code failure pattern reported for developers trying to fix claude code cli hanging on startup when .credentials.json has corrupted scopes field, preventing oauth token refresh. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Fixed in Claude Code v2.1.143 changelog: ‘Fixed a corrupt .credentials.json with a non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh’. This is a known issue with clear error signature and fix. Category mapped to AI Coding Tools per Claude Code -> AI Coding Tools rule.

Common causes

• Fixed in Claude Code v2.1.143 changelog: ‘Fixed a corrupt .credentials.json with a non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh’. This is a known issue with clear error signature and fix. Category mapped to AI Coding Tools per Claude Code -> AI Coding Tools rule.

Quick fixes

1. Confirm the exact error signature matches corrupt .credentials.json with non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

Evidence note: Fixed in Claude Code v2.1.143 changelog: ‘Fixed a corrupt .credentials.json with a non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh’. This is a known issue with clear error signature and fix. Category mapped to AI Coding Tools per Claude Code -> AI Coding Tools rule.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact corrupt .credentials.json with non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without corrupt .credentials.json with non-array scopes value hanging the CLI on startup or silently aborting OAuth token refresh.