You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.0.3 default approval_policy fails thread/start with Codex 0.164.0 and 0.165.0-alpha.1
#134
We reproduced a startup compatibility issue with the official Symphony Elixir v0.0.3 release and Codex 0.164.0 / 0.165.0-alpha.1.
When codex.approval_policy is omitted, Symphony supplies a reject object that these Codex versions reject at thread/start with JSON-RPC error code -32600. Explicitly setting approval_policy: on-request allows the tested thread initialization to succeed, but it is a workaround, not an equivalent replacement for the default's fail-closed behavior.
This default is also documented in the v0.0.3 README.
The failing sequence is:
Use the official Symphony v0.0.3 Elixir release with codex.approval_policy omitted.
Initialize a real Codex app-server.
Start a thread using Symphony's resolved default policy.
Observe thread/start fail with -32600.
We reproduced the default-policy rejection with Codex 0.164.0 on macOS arm64 and Codex 0.165.0-alpha.1 on Linux under WSL. With an explicit on-request policy, initialization and read-only thread creation succeeded in the tested configurations.
This concerns the omitted-setting default, not a claim that every supplied example workflow fails. Workflows that explicitly select another supported policy do not exercise this default.
Workaround and safety semantics
The tested configuration override was:
codex:
approval_policy: on-request
This avoids the schema rejection, but should not be treated as preserving the default's safety semantics or as a blanket recommendation for unattended deployments.
The Codex 0.164.0 approval-policy definition supports granular, rather than the reject object used here. Its granular booleans permit a category when true and reject it when false. Merely renaming reject to granular while retaining the true values would therefore change the intended behavior.
Validation scope
These were local compatibility checks against real Codex binaries. Separate local/synthetic regression checks covered tool roundtrips and same-thread continuation. No hosted model inference was performed, and these results do not establish full tracker orchestration, live cancellation, or compaction behavior.
Requested fix
Could Symphony:
Use a Codex-compatible default that preserves the intended fail-closed behavior.
Add regression coverage for omitted approval_policy, including serialization and real app-server thread/start compatibility.
Document supported Codex versions and migration guidance for existing workflows.
A clear diagnostic for unsupported policy/version combinations would also help distinguish this failure from tracker or model-provider problems.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Summary
We reproduced a startup compatibility issue with the official Symphony Elixir v0.0.3 release and Codex 0.164.0 / 0.165.0-alpha.1.
When
codex.approval_policyis omitted, Symphony supplies arejectobject that these Codex versions reject atthread/startwith JSON-RPC error code-32600. Explicitly settingapproval_policy: on-requestallows the tested thread initialization to succeed, but it is a workaround, not an equivalent replacement for the default's fail-closed behavior.Default and reproduction
The v0.0.3 configuration schema supplies this policy when the setting is omitted:
{"reject":{"sandbox_approval":true,"rules":true,"mcp_elicitations":true}}This default is also documented in the v0.0.3 README.
The failing sequence is:
codex.approval_policyomitted.thread/startfail with-32600.We reproduced the default-policy rejection with Codex 0.164.0 on macOS arm64 and Codex 0.165.0-alpha.1 on Linux under WSL. With an explicit
on-requestpolicy, initialization and read-only thread creation succeeded in the tested configurations.This concerns the omitted-setting default, not a claim that every supplied example workflow fails. Workflows that explicitly select another supported policy do not exercise this default.
Workaround and safety semantics
The tested configuration override was:
This avoids the schema rejection, but should not be treated as preserving the default's safety semantics or as a blanket recommendation for unattended deployments.
The Codex 0.164.0 approval-policy definition supports
granular, rather than therejectobject used here. Its granular booleans permit a category whentrueand reject it whenfalse. Merely renamingrejecttogranularwhile retaining thetruevalues would therefore change the intended behavior.Validation scope
These were local compatibility checks against real Codex binaries. Separate local/synthetic regression checks covered tool roundtrips and same-thread continuation. No hosted model inference was performed, and these results do not establish full tracker orchestration, live cancellation, or compaction behavior.
Requested fix
Could Symphony:
approval_policy, including serialization and real app-serverthread/startcompatibility.A clear diagnostic for unsupported policy/version combinations would also help distinguish this failure from tracker or model-provider problems.
All reactions