Repository navigation
docs: say a config fragment cannot install a Codex profile, and how to keep one #2604
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -419,6 +419,16 @@ Where a fragment's table is one the user already declares, the user's table | |
| wins: the managed table is dropped, their values are never merged, rewritten or | ||
| overwritten, and the rest of the fragment still applies. | ||
|
|
||
| **A fragment can't install a named Codex profile.** Codex versions with named | ||
| profiles read each one from its own file, `<CODEX_HOME>/<name>.config.toml`, | ||
| with top-level keys, and won't load a profile while `config.toml` still holds a | ||
| legacy `[profiles.<name>]` table. A fragment only adds tables to `config.toml`, | ||
| so neither form works there. Create the profile file yourself and select it with | ||
| the member's `codex_config_profile`; see "Codex: select sandbox and approvals | ||
| together" in [getting-started.md](getting-started.md#codex-select-sandbox-and-approvals-together). | ||
| Before a launch or restore, OpenRig checks that a selected profile loads, and for | ||
| a legacy table it names the file to move the settings into. | ||
|
Comment on lines
+429
to
+430
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Clarify that preflight accepts a missing profile file. The native probe succeeds when
|
||
|
|
||
| ### Resource Path Rules | ||
|
|
||
| - All resource paths must be safe relative paths (no `..` traversal, no absolute paths), except a plugin's | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
Repository: mvschwarz/openrig
Length of output: 2045
Script executed:
Repository: mvschwarz/openrig
Length of output: 41880
Web query:
OpenAI Codex CLI 0.130.0 0.134.0 named profile separate file profiles config.toml versionResult:
Script executed:
Repository: mvschwarz/openrig
Length of output: 28788
Script executed:
Repository: mvschwarz/openrig
Length of output: 21989
Script executed:
Repository: mvschwarz/openrig
Length of output: 18428
Script executed:
Repository: mvschwarz/openrig
Length of output: 17194
Qualify the profile-file requirement by Codex version.
Codex 0.130.0 reads named profiles from
[profiles.<name>]. If a user creates only the separate file, preflight can pass but the profile launch can fail. Scope this guidance to Codex 0.134.0 and later, and tell users of older versions to upgrade.Suggested fix
Add after the paragraph: