Exact error
Match the message before using the fix
failed to reload config: missing escaped value, expected `b`, `e`, `f`, `n`, `r`, `\`, `"`, `x`, `u`, `U`Quick answer
Start here
A Windows backslash inside a double-quoted TOML string starts an escape sequence. Change the path to forward slashes or use a TOML single-quoted literal string, then restart Codex. Back up config.toml before editing it.
Diagnosis
Why it happens
- TOML basic strings interpret backslashes as escapes.
- A path such as `C:\Users\name` can therefore contain an invalid escape and stop configuration reload.
Safest first
Fixes, in order
Use forward slashes
Applies when: Simplest fix for most Windows paths
Windows APIs commonly accept forward slashes, and TOML no longer treats them as escapes.
- Back up config.toml.
- Change each affected path from backslashes to forward slashes.
- Save the file and restart Codex.
path = "C:/Users/name/project"Expected: Codex reloads configuration without the missing-escaped-value parser error.
Use a TOML literal string
Applies when: Use when you need to keep Windows backslashes
Single-quoted TOML strings do not process backslash escapes.
- Replace the double quotes around the path with single quotes.
- Keep the Windows path unchanged inside the literal string.
- Restart Codex.
path = 'C:\Users\name\project'Expected: The path parses literally and Codex starts normally.
Verification
Prove the fix worked
- Restart Codex completely.
- Confirm the configuration reload error is absent.
- Use the feature that consumes the edited path and confirm it resolves the intended directory.
Escalation
If it still fails
- Temporarily move the last edited configuration block aside to isolate another TOML syntax error.
- Validate all quoted Windows paths, not only the path named nearest the visible error.
- Do not remove quotes from paths containing spaces.
Scope
Environment and version notes
- The first-hand report used Codex Desktop 26.803.5235 on Windows.
- The path fix follows TOML 1.0 string rules and is not Codex-specific magic.
- Sources rechecked August 20, 2026.
Evidence
Sources
Source labels describe the evidence available on the checked date. A closed issue is not automatically a shipped fix.