openai/codex · error · OAuthStoreLockFailure

timed out after {acquire_timeout:?} waiting for MCP OAuth {s

Error message

timed out after {acquire_timeout:?} waiting for MCP OAuth {store} aggregate-store lock {}

What it means

Error "timed out after {acquire_timeout:?} waiting for MCP OAuth {store} aggregate-store lock {}" thrown in openai/codex.

Source

Thrown at codex-rs/rmcp-client/src/oauth/store_lock.rs:188

        store: OAuthStore,
        #[source]
        source: io::Error,
    },
    #[error("failed to create MCP OAuth {store} aggregate-store lock directory {}", path.display())]
    CreateDir {
        store: OAuthStore,
        path: PathBuf,
        #[source]
        source: io::Error,
    },
    #[error("failed to open MCP OAuth {store} aggregate-store lock {}", path.display())]
    Open {
        store: OAuthStore,
        path: PathBuf,
        #[source]
        source: io::Error,
    },
    #[error(
        "timed out after {acquire_timeout:?} waiting for MCP OAuth {store} aggregate-store lock {}",
        path.display()
    )]
    Timeout {
        store: OAuthStore,
        path: PathBuf,
        acquire_timeout: Duration,
    },
    #[error("failed to lock MCP OAuth {store} aggregate-store lock {}", path.display())]
    Lock {
        store: OAuthStore,
        path: PathBuf,
        #[source]
        source: io::Error,
    },
}

fn oauth_store_lock_path(codex_home: &Path, store: OAuthStore) -> PathBuf {

View on GitHub (pinned to 339751715c)

When it happens

Trigger: Thrown at codex-rs/rmcp-client/src/oauth/store_lock.rs:188 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

AI-assisted analysis of openai/codex@339751715c (2026-08-25). Data as JSON: /api/errors/49c9c1f1bcb31c48. Report an issue: GitHub.