Menu

Post image 1
Post image 2
1 / 2
0

The YAML bug that taught me what bidirectional sync between Claude Code and Codex actually costs

DEV Community·MAXX·21 days ago
#7S8KeGlB
#claudecode#openai#opensource#cli#yaml#file
Reading 0:00
15s threshold

The Codex agent had no name The sync ran clean. Exit code 0. The skill file I'd authored on the Claude side showed up at the matching path on the Codex side, byte-for-byte where I expected it. I opened the Codex agent picker and the entry was there, but its name was the empty string. Just a blank row. I assumed I'd mis-named something on disk. I hadn't. The file had name: code-review at the top, in plain YAML frontmatter, exactly the way Claude writes it. The string was right there. The Codex parser was just refusing to see it. The culprit was one line three rows down: globs: **/*.{js,ts} . Claude's YAML loader is lenient. It reads the value as a string and moves on. Codex uses a strict YAML 1.2 parser, which sees the leading * as an alias anchor, fails to parse the scalar, and silently drops the entire frontmatter block. Every field, including name , goes empty. The fix is one substitution.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More