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
Codex 0.160 camelCase rate limits are not recognized by Symphony (fix available)
#131
Symphony does not recognize the camelCase rate-limit snapshots emitted by Codex CLI 0.160.0. Its state API returns rate_limits: null, so the web dashboard reports rate limits as unavailable even though Codex emits account/rateLimits/updated notifications.
Confirmed on Symphony v0.0.3 and main at be10a1b79df723d6d7612b5651c8522704dafb2e.
Reproduction
Run Symphony with Codex CLI 0.160.0 and an authenticated ChatGPT account.
Start an issue and observe Codex rate-limit notifications.
Read /api/v1/state: rate_limits remains null.
Compare the payload shape from account/rateLimits/read with the parser.
Current Codex snapshots contain limitId, limitName, primary.usedPercent, primary.windowDurationMins, primary.resetsAt, secondary, and credits.hasCredits. The orchestrator's rate_limits_map?/1 recognizes only snake_case identifiers (limit_id / limit_name). Terminal status rendering also misreads camelCase identifiers and credits, and falls back to raw maps for percentage buckets.
Expected
Accept current Codex snapshots, display their limits, and preserve existing snake_case/atom compatibility.
The fix is limited to field compatibility and terminal formatting; it does not change approvals, sandbox, retries, or provider behavior. Fixtures are synthetic and contain no real account/quota data.
Two complete targeted ExUnit files: 50 tests, 0 failures with the fix; the same tests against original main library code: 50 tests, 2 failures reproducing both regressions. Formatting, public @spec checks, and git diff --check pass.
Tests used an isolated bundled OTP VM with official Elixir 1.19.5 Mix/ExUnit; changed modules were compiled from source and other dependencies used release BEAMs. Full make -C elixir all was not run. The installed runtime was not patched.
Web dashboard follow-up
The same contribution branch now replaces the raw Elixir dump with accessible usage bars, explicit used/remaining percentages, duration-based window labels, UTC reset dates, and live countdowns. Missing/null/malformed fields are handled gracefully. CamelCase/snake_case and string/atom keys remain supported.
Targeted validation now covers 54 tests, 0 failures, including connected Phoenix LiveView snapshot refresh and countdown ticks. Full make all remains unrun; the same isolated toolchain limitations apply.
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.
Uh oh!
There was an error while loading. Please reload this page.
Bug
Symphony does not recognize the camelCase rate-limit snapshots emitted by Codex CLI 0.160.0. Its state API returns
rate_limits: null, so the web dashboard reports rate limits as unavailable even though Codex emitsaccount/rateLimits/updatednotifications.Confirmed on Symphony v0.0.3 and main at
be10a1b79df723d6d7612b5651c8522704dafb2e.Reproduction
/api/v1/state:rate_limitsremainsnull.account/rateLimits/readwith the parser.Current Codex snapshots contain
limitId,limitName,primary.usedPercent,primary.windowDurationMins,primary.resetsAt,secondary, andcredits.hasCredits. The orchestrator'srate_limits_map?/1recognizes only snake_case identifiers (limit_id/limit_name). Terminal status rendering also misreads camelCase identifiers and credits, and falls back to raw maps for percentage buckets.Expected
Accept current Codex snapshots, display their limits, and preserve existing snake_case/atom compatibility.
Proposed fix and regression evidence
Prepared contribution:
The fix is limited to field compatibility and terminal formatting; it does not change approvals, sandbox, retries, or provider behavior. Fixtures are synthetic and contain no real account/quota data.
Two complete targeted ExUnit files: 50 tests, 0 failures with the fix; the same tests against original main library code: 50 tests, 2 failures reproducing both regressions. Formatting, public
@specchecks, andgit diff --checkpass.Tests used an isolated bundled OTP VM with official Elixir 1.19.5 Mix/ExUnit; changed modules were compiled from source and other dependencies used release BEAMs. Full
make -C elixir allwas not run. The installed runtime was not patched.Web dashboard follow-up
The same contribution branch now replaces the raw Elixir dump with accessible usage bars, explicit used/remaining percentages, duration-based window labels, UTC reset dates, and live countdowns. Missing/null/malformed fields are handled gracefully. CamelCase/snake_case and string/atom keys remain supported.
Commit: LanceCake@62894fe
Targeted validation now covers 54 tests, 0 failures, including connected Phoenix LiveView snapshot refresh and countdown ticks. Full make all remains unrun; the same isolated toolchain limitations apply.
All reactions