All tools

Codex CLI Connection Checker

Diagnose Codex CLI sign-in and connection errors from terminal output, including 401, 403 and timeouts.

Processing happens in your browser. Your inputs, files and results stay on this device.

Codex terminal output

Paste codex login status or the relevant error. Remove keys and tokens.

Connection diagnosis

A likely cause and next step will appear here.

Why is Codex CLI not working?

Start with codex --version and codex login status. If the CLI reports that you are signed in, paste the request error to check the next step.

“Not logged in” points to local authentication. A 403 on a request calls for a separate access check.

Limitations

The browser checks the text you provide. Account, model and network access require a separate check.