docs(codex): extraConfig Helm example is not implemented by the chart

[maxpshaw]

Description

docs/codex.md documents enabling Codex auto-review via Helm with:

--set-json 'agents.codex.extraConfig={"sandbox":{"approval_policy":"auto-review"}}'

However, the published Helm charts I tested do not render agents.codex.extraConfig into the Kubernetes manifest or into /home/node/.codex/config.toml.
Tested chart versions:

• openab-0.8.2
• openab-0.8.3-beta.4

In both versions, helm show values openab/openab --version does not list extraConfig, and rendering the chart with agents.codex.extraConfig.sandboxapproval_policy=auto-review does not produce
approval_policy or auto-review in the manifest.

Current working deployments therefore need to use agents.codex.extraInitContainers to mutate /home/node/.codex/config.toml, for example by writing:

[sandbox]
approval_policy = "auto-review"

This makes the docs/codex.md Helm example misleading: it suggests a declarative Helm values path that does not appear to be implemented in the released chart.

Suggested Change

Either:

1. Implement agents..extraConfig in the Helm chart so the documented example works for Codex, or
2. Update docs/codex.md to document the currently supported Helm approach using agents.codex.extraInitContainers.

If extraConfig is planned but not released yet, the docs should mention the minimum chart version that supports it.

[CHC-Agent]

Issue at a Glance

docs/codex.md (line 218)
┌──────────────────────────────────────────────────┐
│ --set-json 'agents.codex.extraConfig=          │
│   {"sandbox":{"approval_policy":"auto-review"}}'│
│                                                  │
│ Documents extraConfig as a Helm values path      │
└──────────────────────────┬───────────────────────┘
                           │ but...
                           ▼
┌──────────────────────────────────────────────────┐
│ charts/openab/values.yaml                        │
│ ❌ No extraConfig key defined                    │
│                                                  │
│ charts/openab/templates/configmap.yaml           │
│ ❌ No template logic to render extraConfig       │
└──────────────────────────────────────────────────┘

Working alternative (undocumented for this use case):
  agents.codex.extraInitContainers → write config.toml

Hi @maxpshaw,

Confirmed — charts/openab/values.yaml does not define agents.<name>.extraConfig and templates/configmap.yaml has no logic to render it. The docs/codex.md Helm example at line 218 references a values path that does not exist in chart versions 0.8.2 or 0.8.3-beta.4. The documented --set-json invocation is silently ignored by Helm.

The chart does support extraInitContainers (values.yaml line 342) which can be used as a workaround to write /home/node/.codex/config.toml at pod startup.

Related:

• No existing issues or PRs for extraConfig implementation.

Either the chart needs to implement extraConfig or the docs should be updated to document the extraInitContainers approach. A PR to fix this is welcome — feel free to open one if you are interested.