Fix Codex config.toml “missing escaped value” on Windows

A double-quoted Windows path makes TOML interpret backslashes as escapes. Forward slashes or literal single-quoted TOML strings fixed the reported startup failure.

Quick answer

Replace backslashes with forward slashes inside a double-quoted TOML path, or keep the backslashes and use a single-quoted TOML literal string. Save and restart Codex.

The exact error

missing escaped value, expected b, e, f, n, r, \, quote, x, u, U

Do not use this guide for a merely similar message. The workaround is scoped to this signature and the environments below.

Match your environment

  • Codex Desktop
  • Windows path in config.toml
  • Startup spinner or config reload failure

What to do

  1. 01

    Back up config.toml

    Make a copy before editing so you can restore unrelated MCP and feature settings.

  2. 02

    Find the double-quoted Windows path

    In a TOML basic string, sequences beginning with a backslash are parsed as escapes.

    command = "C:\Users\you\tools\server.exe"
  3. 03

    Use forward slashes

    Windows applications generally accept forward slashes here, and the reporter confirmed this form works.

    command = "C:/Users/you/tools/server.exe"
  4. 04

    Or use a literal TOML string

    Single-quoted TOML strings preserve backslashes instead of treating them as escape sequences.

    command = 'C:\Users\you\tools\server.exe'
  5. 05

    Restart and verify

    Save the file, fully restart Codex, and confirm the config reload error is gone before changing another setting.

What likely happened

This is TOML parsing behavior, not a missing file. Backslashes have special meaning inside double-quoted TOML strings, so a normal-looking Windows path can create an invalid escape.

First-hand sources

Source links support the environment and workaround claims above. An issue being closed does not by itself mean a fix shipped.