codex-config 0.1.0 → 0.144.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,40 +1,90 @@
1
1
  # codex-config
2
2
 
3
- Apply a `config.toml.template` to `~/.codex/config.toml` without taking over the whole file.
3
+ Keep the active Codex `config.toml` current for the GPT-5.6 model family while preserving unrelated user settings such as MCP servers, projects, providers, and notices. The default target is `$CODEX_HOME/config.toml`, with `~/.codex/config.toml` used when `CODEX_HOME` is unset.
4
4
 
5
- By default, `codex-config` only adds template options that are missing. Existing options stay unchanged, and unrelated tables such as `[mcp_servers.*]`, `[model_providers.*]`, `[notice]`, and `[projects.*]` are preserved.
5
+ The bundled configuration defaults to `gpt-5.6-sol`. The supported models are:
6
6
 
7
- Use `--override-all` to reset template-covered options to the template values.
7
+ - `gpt-5.6-sol`
8
+ - `gpt-5.6-terra`
9
+ - `gpt-5.6-luna`
8
10
 
9
- ## Run
11
+ GPT-5.6 models carry their own personality instructions and do not expose a selectable personality placeholder. `codex-config` therefore removes the ineffective top-level `personality` setting.
12
+
13
+ The template explicitly opts into memories. Newly stable Codex capabilities such as multi-agent, goals, image generation, plugins, and tool search behavior are left at their source defaults, so the config does not pin redundant feature flags. Under-development features are not enabled automatically.
14
+
15
+ Package release versions track the Codex CLI version used for live compatibility testing.
16
+
17
+ ## Apply
10
18
 
11
19
  ```bash
12
- npx codex-config apply
20
+ pnpm dlx codex-config apply
13
21
  ```
14
22
 
15
- ## Usage
23
+ By default, missing template settings are added and existing values are preserved, except for compatibility migrations required by the GPT-5.6 target:
24
+
25
+ - unsupported models are changed to `gpt-5.6-sol`;
26
+ - `sandbox_mode` is converted to its equivalent `default_permissions` profile;
27
+ - `personality`, Codex feature flags marked as removed, and historical flags deleted from the source catalog are deleted;
28
+ - legacy feature aliases are renamed, and old web-search toggles become the top-level `web_search` mode;
29
+ - legacy status-line and terminal-title identifiers are canonicalized.
30
+
31
+ Use a dry run to inspect these operations before writing:
16
32
 
17
33
  ```bash
18
- npx codex-config apply
19
- npx codex-config apply --dry-run
20
- npx codex-config apply --override-all
21
- npx codex-config diff
22
- npx codex-config check
23
- npx codex-config doctor
34
+ pnpm dlx codex-config apply --dry-run
24
35
  ```
25
36
 
26
- Optional global install:
37
+ Use `-f` to reset every template-covered setting to the bundled value. Supported model selections such as Terra or Luna are otherwise preserved.
27
38
 
28
39
  ```bash
29
- npm install -g codex-config
30
- codex-config apply
40
+ pnpm dlx codex-config apply -f
41
+ ```
42
+
43
+ ## Inspect
44
+
45
+ ```bash
46
+ pnpm dlx codex-config diff
47
+ pnpm dlx codex-config check
48
+ pnpm dlx codex-config doctor
49
+ ```
50
+
51
+ `doctor` validates TOML against the bundled Codex JSON Schema and reports the exact Codex source revision, supported models, removed, retired, or deprecated features, and non-canonical settings. Add `--json` to any command for machine-readable output.
52
+
53
+ ## Profiles
54
+
55
+ Current Codex profiles are separate config layers named `$CODEX_HOME/<name>.config.toml`. Apply or inspect one directly with the matching option:
56
+
57
+ ```bash
58
+ pnpm dlx codex-config apply --profile work
59
+ pnpm dlx codex-config doctor --profile work
60
+ codex --profile work
31
61
  ```
32
62
 
63
+ The older top-level `profile` selector and `[profiles.<name>]` tables are no longer consumed by current Codex. `doctor` reports them with migration guidance, but does not delete or split that user-owned data automatically.
64
+
33
65
  Options:
34
66
 
35
- - `--target PATH`: target config path, default `~/.codex/config.toml`
67
+ - `--target PATH`: explicit target config path
68
+ - `-p, --profile NAME`: target `$CODEX_HOME/<name>.config.toml`; cannot be combined with `--target`
36
69
  - `--template PATH`: template path, default bundled template
37
- - `--override-all`: overwrite template-covered keys
70
+ - `-f, --force`: overwrite template-covered settings
38
71
  - `--json`: print JSON output
39
72
 
40
- One-shot vibe coded by Codex.
73
+ Optional global installation:
74
+
75
+ ```bash
76
+ pnpm add --global codex-config
77
+ codex-config apply
78
+ ```
79
+
80
+ ## Development
81
+
82
+ ```bash
83
+ pnpm install
84
+ pnpm sync:codex -- --source /path/to/codex
85
+ pnpm test
86
+ pnpm run check
87
+ pnpm run build
88
+ ```
89
+
90
+ `sync:codex` snapshots `config.schema.json`, the GPT-5.6 model capabilities (including minimum client version, reasoning efforts, service tiers, and personality support), and feature lifecycle metadata from the selected Codex checkout. It also reads the full first-parent feature history to retain migrations for keys that Codex deleted outright, so the source checkout must not be shallow. Commit the generated changes together so validation and migrations target one source revision.