Skip to content

chore: sync fork with upstream (resolve codex binary bundled inside ChatGPT.app) - #52

Merged
cte13 merged 1 commit into
mainfrom
chore/sync-upstream-codex-chatgpt-app
Sep 6, 2026
Merged

cte13 merged 1 commit into
mainfrom
chore/sync-upstream-codex-chatgpt-app

Conversation

@cte13

@cte13 cte13 commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Sync

Catches the fork up with chattymin/PokeTokenBar@main (now at 5f1ef52).

git rev-list reports 23 upstream commits not in origin/main, but that is the squash-merge ancestry break already described in #45: the content of 22 of them was applied by #38, #43, and #45. Verified by diffing content rather than the commit list — the remaining differences between the two branches are all fork divergence (iOS companion, widget, Antigravity refresh-token work, phone payload server).

Only one upstream commit is genuinely new, cherry-picked with -x:

No conflicts; the fork's CodexRateLimitsProvider candidate list matches upstream at that point.

Verification

  • ./scripts/test-gate.sh — 1074 tests, 0 failures (12 skipped); logic-core line coverage 91.77% ≥ 75%.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Q7ExQdXA9rxRQEEqv7YC9c

…splay (chattymin#262)

Codex usage is parsed from ~/.codex/sessions logs, but limits are fetched
by spawning the codex CLI (app-server account/rateLimits/read). Users who
run Codex through the ChatGPT desktop app have no standalone codex install,
so limit fetch was skipped ("codex binary not found") while usage still
showed. Add the ChatGPT.app bundled CLI path as the last candidate so
dedicated installs keep precedence.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
(cherry picked from commit 5f1ef52)
@cte13
cte13 merged commit db0fcb9 into main Sep 6, 2026
@cte13
cte13 deleted the chore/sync-upstream-codex-chatgpt-app branch September 22, 2026 01:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants