disable_response_storage=true is not working in codex-rs (rust version)

Resolved 💬 3 comments Opened May 31, 2025 by vjain419 Closed Jun 9, 2025
💡 Likely answer: A maintainer (bolinfest, collaborator) responded on this thread — see the highlighted reply below.

What version of Codex is running?

_No response_

Which model were you using?

o3

What platform is your computer?

Darwin 24.4.0 arm64 arm

What steps can reproduce the bug?

npm i -g @openai/codex@native

  • use api key with ZDR
  • add disable_response_storage = true in config.toml
  • codex --full-auto
  • Say "Hello, Explain me this codebase" -- gives errors.

What is the expected behavior?

_No response_

What do you see instead?

unexpected status 401 Unauthorized

(I confirmed that key works)

Additional information

As per document I added disable_response_storage = true in config.toml and also passed cmd line option as -c both didn't work and I keep getting error as I am using enterprise api key which has ZDR

we had same issue with codex-cli (old version) but cmd line option --disable-response-storage was working for that.

View original on GitHub ↗

3 Comments

bolinfest collaborator · 1 year ago

Ah, OK, I have an OPENAI_API_KEY associated with an org with ZDR enabled and I can repro. Taking a look!

bolinfest collaborator · 1 year ago

@vjain419 Actually, I had my config flipped. Things work if I run the Rust CLI with:

codex --config disable_response_storage=true

It is possible that I fixed this recently as part of https://github.com/openai/codex/pull/1167, so you might want to try the appropriate binary for your platform from https://github.com/openai/codex/releases/tag/codex-rs-45519e12f39777b65c05ed498503ddcb60beb289-1-rust-v0.0.2506030956 (published earlier today).

Indeed, --config disable_response_storage=true worked for me with:

$ codex --version
codex-cli 0.0.2506030956
vjain419 contributor · 1 year ago

Hi @bolinfest I can confirm that disable_response_storage this is working now with latest version.