Codex trying to read ~/.keychain on every command

Resolved 💬 1 comment Opened Apr 26, 2026 by cloudhead Closed Jun 2, 2026

What version of Codex CLI is running?

0.125.0

What subscription do you have?

Pro Lite

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 6.19.12-arch1-1 x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Kitty

What issue are you seeing?

Almost every command gives output like this, about trying to read .keychain, I have no idea why.

• Ran cargo fmt
  └ /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system

• Ran timeout 10 git status --short
  └ /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    … +5 lines (ctrl + t to view transcript)
    M  test/runner.rad
    ?? freestanding-impl.md

• Ran timeout 10 git diff --cached --stat
  └ /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    … +5 lines (ctrl + t to view transcript)
     test/runner.rad            | 37 ++++--------------------------------
     6 files changed, 66 insertions(+), 87 deletions(-)

• Ran timeout 10 git diff --cached --name-only
  └ /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    /usr/bin/keychain: line 444: /home/cloudhead/.keychain/desktop-sh.foo: Read-only file system
    … +4 lines (ctrl + t to view transcript)

What steps can reproduce the bug?

Just ask it to run some git or cargo commands in a repo.
I'll also note that I've had this issue since I started using codex a few months ago, so it's not a newly introduced bug.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗