Omniscio

OmniscioGuidesOAuth token refresh failed

Claude Code: failed to refresh OAuth token

Last checked against Anthropic's documentation on November 14, 2026. By the Omniscio team. Updated .

What does the message look like?

In an interactive session you get this one line:

Could not refresh your login because another Claude Code process is refreshing it (or exited mid-refresh) · Try again in a minute; if it keeps happening, close other Claude Code windows or sign in again with /login

In a script, claude -p, or the Agent SDK, the same failure reads:

Failed to refresh OAuth token: another Claude Code process is refreshing it or exited mid-refresh. This is usually transient; retry in a minute, and if it persists close other Claude Code processes or sign in again

Both lines say the same thing. Only the wording changes.

What does it actually mean?

Your saved claude.ai login had expired and needed renewing. Renewing it takes a lock that every Claude Code process on the machine shares.

Another process held that lock. Or it exited halfway through and left the lock behind. Either way, the refresh made no progress while this session waited, so Claude Code stopped the request before sending it.

The important part: your login was not rejected. Nothing is wrong with your account.

How do I fix it?

Work down this list. Most people are done after the first step.

  1. Try again in a minute. If the other window finishes the refresh first, this session picks up the renewed login on its own.
  2. Close your other Claude Code windows, then retry. Do this if the message keeps coming back.
  3. Run /login. Do this if it returns with no other Claude Code window open. Signing in again does not wait on the refresh lock.

/login is typed into Claude Code's own chat box, the place you type messages, with a slash in front, then Enter.

Why does it happen when I run several sessions at once?

The renewal lock is shared by every Claude Code window on the machine. When one window renews the login, the others have to wait for it.

If that window is slow, or closes halfway through, the waiting ones give up with this message. Waiting a minute, or closing the extra windows, clears it.

If you run many sessions, close the ones you are not using before you expect a login to renew. That leaves the lock free for the session that needs it.

What if my message says the disk is full?

That is a different error with a different fix. Free space on the disk that holds your Claude Code settings, then send your message again. Signing in will not help while the disk is full, because a new login could not be saved.

This page covers the version that names another Claude Code process.

Common questions

What does 'failed to refresh OAuth token: another Claude Code process is refreshing it' mean?

Your saved claude.ai login had expired and needed renewing. Another Claude Code process on the same machine held the shared refresh lock, or exited and left it behind, so the refresh made no progress while this session waited. Claude Code stops the request before sending it. It does not mean your login was rejected.

Do I need to sign in again?

Not at first. Try again in a minute. If another process finishes the refresh, this session uses the renewed login on its own. Sign in with /login only if the message keeps coming back and no other Claude Code process is running.

Why does it happen when I run several Claude Code sessions at once?

The refresh lock is shared by every Claude Code process on the machine. When one session renews the login, the others wait for it. If that process is slow, or exits halfway through, the waiting sessions give up with this message. Waiting a minute or closing the extra windows clears it.

Is this the same as the disk-full login message?

No. The disk-full version says the config directory or your disk quota is full. Freeing space is the fix for that one, and signing in again will not help. This page covers the version that names another Claude Code process.

Where these answers come from