Skip to content
CC Switch WikiUnofficial Community Wiki

AbsolutePathBuf deserialized without a base path - Codex

Quick fix

On Codex for macOS, relative paths written by cc-switch cause this error. Change model_catalog_json in ~/.codex/config.toml to an absolute path.

Symptom

Section titled “Symptom”
Error output
创建任务时出错
invalid configuration: AbsolutePathBuf deserialized without a base path
in `model_catalog_json`
English translation

Error creating task invalid configuration: AbsolutePathBuf deserialized without a base path in `model_catalog_json`

Cause

Section titled “Cause”

Since cc-switch v3.16.2, the program writes `model_catalog_json` as a relative path (such as `cc-switch-model-catalog.json`). This works on WSL/Windows, but when Codex desktop starts on macOS, the missing base path causes deserialization to fail and throws this error. The issue exists from cc-switch v3.16.2 through v3.19.0 and recurs every time cc-switch writes the configuration.

Fix

Section titled “Fix”

  1. Open the Codex configuration file `~/.codex/config.toml`.

  2. Find the `model_catalog_json` field and change it from a relative path to an absolute path (replace `<user>` with your actual macOS username).

    ~/.codex/config.toml
    model_catalog_json = "cc-switch-model-catalog.json"
    model_catalog_json = "/Users/<user>/.codex/cc-switch-model-catalog.json"

  3. Alternatively, run the following command in the macOS terminal to replace it in one step: ```bash sed -i '' 's|model_catalog_json = "cc-switch-model-catalog.json"|model_catalog_json = "'"$HOME"'/.codex/cc-switch-model-catalog.json"|' ~/.codex/config.toml ```

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version0.144.1 / 26.721.41059
PlatformsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
Why does this not happen on Windows/WSL?
Codex can correctly resolve the relative path written by cc-switch on Windows/WSL, but the macOS desktop client strictly requires an absolute path during deserialization, so the error occurs only on macOS.
Will restoring a database backup through cc-switch fix it?
One user reported that restoring the latest database backup temporarily restored normal operation, but this is not a root fix. The issue recurs every time cc-switch writes the configuration, so you must manually change the configuration file to an absolute path.
What if the configuration also shows `url is not supported for stdio`?
This is another known issue with cc-switch MCP sync. When writing back `config.toml`, it incorrectly appends HTTP fields to an existing stdio entry. Manually edit `~/.codex/config.toml`, remove the conflicting `command`, `args`, and `type = "stdio"` fields, and keep only the `url`-related configuration.
Section titled “Related problems”
Codex provider API keys overwrite each other after a restart or switchEnable CC Switch local proxy takeover, or use experimental_bearer_token in config.toml, to bypass the auth.json sync defect.7 issues mergedGeneral config has no effect and gets overwritten by earlier config - Codex CC SwitchUpgrade to CC Switch v3.17.0+ to fix Codex general-config merging. If an old snapshot still overwrites it, switch to another provider and back to self-heal.21 issues mergedconfig.toml and auth.json still hold the previous third-party APIUpgrade CC Switch to v3.16.1+, restart, and switch Codex provider again. If official OAuth broke, run codex logout then codex login --device-auth.11 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.