From 33d50234a8ceaeea9d6bd86b3dd8e4cf59e3bdf7 Mon Sep 17 00:00:00 2001 From: "Adam Perry @ OpenAI" Date: Tue, 16 Jun 2026 14:05:32 -0700 Subject: [PATCH] Record invariants for path migration. (#28589) ## Why Help Codex understand how to execute the migration to support cross-OS paths. ## What Expand the path-types skill with our goals and constraints. --- .codex/skills/path-types/SKILL.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/.codex/skills/path-types/SKILL.md b/.codex/skills/path-types/SKILL.md index bc3809d3d..ccf1a9f41 100644 --- a/.codex/skills/path-types/SKILL.md +++ b/.codex/skills/path-types/SKILL.md @@ -18,3 +18,22 @@ migration; if compliance is difficult, ask the user how to proceed. cases. - Tool call arguments that the model is expected to generate should be deserialized as regular `String`s with feature-specific path handling code. + +## Migration requirements + +Keep these requirements in mind while migrating code to conform with the above guidelines: + +* existing app-server clients keep sending and receiving legacy native-path strings +* app-server can retain and manipulate foreign-platform path URIs +* exec-server APIs use file:// URIs +* local-only operation must not change model-visible text +* model tool arguments may contain raw relative or absolute paths for any OS +* path reasoning must work before the related environment has come online +* URIs cannot explicitly encode the executor’s path convention or operating system +* users must not configure the environment’s OS/path convention explicitly + +It is OK if the conversion between paths and URIs is somewhat lossy as long as it will do the right +thing for real users. + +Migrating to URIs should not add significant new failure modes. We will need to surface errors in +some places that were previously infallible but it should be kept to a minimum.