codex CLI login not working on macOS: what fixed it

TL;DR:

codex CLI login not working on macOS: what fixed it

Symptom: codex --version fails with "No such file or directory", while codex login and codex exec throw 401 Unauthorized or "Not inside a trusted directory".

Cause: brew cask leaves only symlinks with missing binaries, expired tokens in auth.json, and security restrictions blocking non-git directories.

Fix: Run brew reinstall --cask codex to restore the binary, re-run codex login for a fresh token, and append --skip-git-repo-check when working outside repositories.

Why codex login alone did not clear the 401

I spent hours trying to get the codex CLI working after a clean install. The first red flag appeared when I ran codex --version. Instead of printing the installed version, it immediately crashed with "No such file or directory". This is a classic symptom of a broken package manager installation. When you install tools through brew cask, the system sometimes only writes symbolic links instead of copying the actual executable files. A symbolic link is just a reference path that points to another file, so if the target disappears, the link becomes useless. It felt like checking a skeleton and finding nothing inside.

Running brew reinstall --cask codex fixed the missing binary and restored the symlinks. codex --version started working again, which made me confident I had fixed the installation. Then came codex login. Every attempt returned 401 Unauthorized. I assumed the API key was invalid and went through the reissuing process, but the error persisted. The real issue lived inside auth.json, which stores your authentication tokens on disk. Authentication tokens are temporary credentials that prove your identity to the service. Package updates or manual edits can leave these tokens expired on disk. Running codex login again forces the CLI to generate a fresh token and overwrite the stale entry. It cleared the 401 Unauthorized response immediately.

Breaking the trusted directory check for local projects

The final hurdle appeared when I tried codex exec. Running it outside a version-controlled project triggered "Not inside a trusted directory" and refused to execute. This is not a bug; it is a built-in security measure. The CLI defaults to running only in directories that contain git commit history, assuming those are validated codebases. When I tried to apply the tool to private files or scratch projects, it blocked me without warning.

I had to dig into man codex to find the override. Adding --skip-git-repo-check disables that directory validation and lets the command run anywhere you specify. Testing codex exec --skip-git-repo-check confirmed it worked exactly as intended. After verifying that codex login succeeded and codex --version printed correctly, I stopped fighting the toolchain.

Dealing with broken symlinks, expired tokens, and hidden security checks simultaneously taught me a practical lesson. CLI failures rarely come from a single missing dependency. Package managers, local config files, and default security policies interact in ways that simple reinstallation cannot fix. You have to trace each error back to its actual source before applying the next command. Understanding how your package manager and tool defaults interact saves more time than memorizing error codes.

Related posts

Comments

Post a Comment

Popular posts from this blog

npm command not found on Windows: fix the PATH

Image
I recently hit a wall while configuring my development environment on Windows. It's one of those subtle issues that can waste an afternoon if you don't know what to look for. Here's exactly how I diagnosed and fixed a 'command not found' error after a successful global install. The Problem I decided to add a markdown processing tool to my toolkit by running: npm install -g markdown-it-cli The terminal output confirmed the installation succeeded, displaying a message about added packages. Satisfied, I tried to use it by typing markdown-it-cli in the command line. Windows immediately responded with: 'markdown-it-cli is not recognized as an internal or external command, operable program or batch file.' This error means Windows looked through every folder in its search list and couldn't find an executable with that name. Attempts and Failures My initial reaction was to suspect the package itself might be broken. I tried running it using npx , wh...
Read more

Codex CLI 401 Unauthorized and Installation Fixes

Image
I recently spent several frustrating hours troubleshooting the Codex CLI on my Mac. It was a classic developer trap: fixing one problem immediately revealed another. Broken symlinks, expired tokens, and directory permissions converged, making it feel as though the tool was simply broken. Since "codex 401 unauthorized" is one of the most searched terms on my blog, it's clear many others are hitting these same walls. I have documented the exact sequence of failures and fixes I encountered on my Mac mini to help you avoid the rabbit hole. Why does codex --version say No such file or directory? When I first installed Codex via Homebrew Cask, the installation appeared successful. However, running codex --version returned No such file or directory . It turned out that while the symbolic link existed, the executable it pointed to was missing. The shell had a map to the binary, but the destination was empty. To fix this, you must restore both the link and the executable vi...
Read more

Claude CLI 401 Unauthorized Refresh Token Issue

Symptom: claude commands fail with 401 Unauthorized and the message "refresh token was already used. Please log out and sign in again." Cause: The refresh token expired after being consumed by another session or a background process. Refresh tokens are single-use credentials. Fix: Run claude auth login to refresh authentication without running a logout command first. Why claude login alone did not clear the 401 I was running a pipeline command when every subsequent CLI call failed. The terminal returned this exact output: Error: 401 Unauthorized Message: "Authentication failed: refresh token was already used. Please log out and sign in again." Code: "AUTH_ERROR" The error text explicitly instructs me to log out. I spent roughly ten minutes searching the terminal for a logout function. The prompt only showed AUTH_ERROR . I assumed clearing old sessions was required first. That assumption blocked progress. The instructions in the error message ...
Read more