Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix TUI trust prompt hides config/batchWrite failure cause when setting project trust

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

config error. The failed operation is trying to persist project trust to the 3. Observe the error: The TUI should include the underlying config/batchWrite server error, for or otherwise surface the JSON-RPC error message/data so the user can

Root Cause

This message is not actionable because it hides the underlying app-server/ config error. The failed operation is trying to persist project trust to the user config, equivalent to:

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.135.0

What subscription do you have?

corporate

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 5.15.0-316.196.4.1.el8uek.x86_64 x86_64 x86_64

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

macOS Terminal.app, SSH to Linux host

Codex doctor report

What issue are you seeing?

When starting Codex in an untrusted directory and selecting the option to trust the directory, the TUI shows only:

Failed to set trust for <my_cwd_path>: config/batchWrite failed in TUI

This message is not actionable because it hides the underlying app-server/ config error. The failed operation is trying to persist project trust to the user config, equivalent to:

[projects."<my_cwd_path>"] trust_level = "trusted"

What steps can reproduce the bug?

  1. Start Codex in a directory that is not already trusted, for example:

    cd <my_cwd_path> codex

  2. At the TUI trust prompt, select the option to trust/continue.

  3. Observe the error:

    Failed to set trust for <my_cwd_path>: config/batchWrite failed in TUI

What is the expected behavior?

The TUI should include the underlying config/batchWrite server error, for example:

Failed to set trust for <my_cwd_path>: config/batchWrite failed in TUI: <server-side cause>

or otherwise surface the JSON-RPC error message/data so the user can distinguish readonly config, invalid config, app-server failure, and validation failures.

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix TUI trust prompt hides config/batchWrite failure cause when setting project trust