From bd2a78632665006149d6e7df627c52ebc1b3464e Mon Sep 17 00:00:00 2001 From: "Adam Perry @ OpenAI" Date: Tue, 16 Jun 2026 15:01:22 -0700 Subject: [PATCH] Tell codex about PathUri serde compat. (#28595) This addresses another wrinkle I keep having to re-prompt codex about when migrating to cross-OS paths. --- .codex/skills/path-types/SKILL.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.codex/skills/path-types/SKILL.md b/.codex/skills/path-types/SKILL.md index ccf1a9f41..de35714dd 100644 --- a/.codex/skills/path-types/SKILL.md +++ b/.codex/skills/path-types/SKILL.md @@ -19,6 +19,13 @@ migration; if compliance is difficult, ask the user how to proceed. - Tool call arguments that the model is expected to generate should be deserialized as regular `String`s with feature-specific path handling code. +## Rollout stability + +Assume that rollouts will be parsed by monotonically increasing versions of Codex. + +You can use `PathUri` in place of `AbsolutePathBuf` for rollout fields without jeopardizing +backwards compatibility since `PathUri` allows deserialization from bare absolute paths. + ## Migration requirements Keep these requirements in mind while migrating code to conform with the above guidelines: