Skip to content

Support chatgpt 26.1103 - #31

Open
imnatann wants to merge 3 commits into
b-nnett:mainfrom
imnatann:support-chatgpt-26.1103
Open

imnatann wants to merge 3 commits into
b-nnett:mainfrom
imnatann:support-chatgpt-26.1103

Conversation

@imnatann

Copy link
Copy Markdown

Summary

Verification

  • npm run check
  • npm run release:check
  • Tested against the upstream build in docs/COMPATIBILITY.md
  • No credentials, account data, app bundles, or unredacted device codes

Security-sensitive changes

Describe any changes to credential handling, subprocesses, network requests,
signing, entitlements, Electron injection, or Computer Use. Write “None” if
there are no such changes.

Router Patch added 3 commits November 10, 2026 13:50
Renderer and main-process anchors are now located by content instead of by
chunk file name, so a build that ships one bootstrap.js plus many
early-bootstrap-* chunks still patches. The injected account menu binds to the
host module's own JSX runtime, React namespace and menu kit under freshly
generated names, so minified host identifiers are no longer shadowed.

The installer forwards its arguments to the patcher and expands the empty
option array safely under macOS /bin/bash 3.2.

The Codex CLI proxy follows the CLI's move to Resources/codex-cli/bin/codex,
and the nested CodexCLI.app, native and framework code are re-signed so a deep
verification passes. The ASAR integrity digest that newer Electron embeds in
the framework is rewritten, and ad-hoc builds drop restricted entitlements and
the hardened runtime.
Bind CH to the menu-kit namespace (D.ms) instead of the kit root: Separator was
undefined, so opening the profile menu crashed the renderer into the
"ChatGPT hit a snag" screen. The injected menu is also wrapped in an error
boundary so a failure inside it hides the router rows rather than the app.

Stop replacing the Codex CLI on builds whose desktop provisions its own
CodexCLI.app copy; the proxy had no effect there and the launch only churned
the copied bundle. The patcher now warns instead of silently doing nothing.
Newer ChatGPT builds provision their own CodexCLI.app copy and run a policy
handshake against it before the profile menu appears. A proxy in either the
bundle or the provisioned copy fails that handshake, so the patcher now leaves
the CLI alone and reports that multiplexing is inactive.

The injected menu returns null when the control service is unreachable, so the
native menu is unchanged instead of showing an error row the user cannot act on.
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.

1 participant