Codex CLI reliance on keychain for OAuth MCPs makes using
Open 💬 1 comment Opened Apr 3, 2026 by El-Fitz
What version of Codex CLI is running?
0.118.0
What subscription do you have?
Pro
Which model were you using?
_No response_
What platform is your computer?
macOS
What terminal emulator and version are you using (if applicable)?
_No response_
What issue are you seeing?
I installed a few OAuth MCPs (painstakingly) for the Codex CLI on my headless Mac mini through VNC.
When after a reboot I launched a Codex session through SSH, none of the MCPs were authenticated.
Turns out, the credentials are stored in the keychain, and that's a ton of pain for auto-login headless ssh setups.
What steps can reproduce the bug?
Install a few OAuth MCPs for the Codex CLI on a headless Mac mini through VNC.
SSH into the machine (maybe reboot first, not clear on the keychain lifecycle), launc a Codex session through SSH, none of the MCPs will be authenticated.
What is the expected behavior?
Keychain reliance should be configurable
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗