Summary
With CodexSplit 2.0.0 on macOS Apple Silicon, native ChatGPT Desktop Computer Use and Cmd+Cmd Appshot can remain unavailable after CodexSplit has been opened and the in-app Restore Native action reports completion.
The native integrations recovered only after fully quitting both apps, resetting the affected Apple Events approval state, and relaunching ChatGPT. The current restore flow therefore does not provide an end-to-end guarantee that the already-running unified ChatGPT process has returned to a healthy native state.
This is a new-version follow-up and is intentionally separate from #32, which covered OpenCodex 1.2.0.
Environment
- macOS 26.6.0, Apple Silicon
- CodexSplit 2.0.0
- ChatGPT Desktop 26.803.41515
- Bundled Codex 0.147.0-alpha.6.5
- Computer Use plugin 1.0.1000633
Reproduction
- Start with native Computer Use and
Cmd+Cmd Appshot working in the unified ChatGPT Desktop app.
- Launch CodexSplit 2.0.0.
- Use CodexSplit's Restore Native action.
- Return to the already-running ChatGPT app.
- Test Appshot and native Computer Use.
Actual behavior
-
Restore Native did not immediately restore a usable native integration in the running ChatGPT process.
-
Appshot/Computer Use remained unavailable until manual recovery and an app restart.
-
The earlier failure path included:
Codex Computer Use Apple Event error -1743: Unknown error
-
Closing only the CodexSplit window is insufficient because the background gateway may continue running; a full quit is required.
Recovery that worked
-
Fully quit CodexSplit and ChatGPT.
-
Confirm that no CodexSplit/OpenCodex global CODEX_CLI_PATH launch environment remains.
-
Reset the affected Apple Events approval state:
tccutil reset AppleEvents com.openai.codex
-
Relaunch ChatGPT.
After this recovery:
- Appshot returned to normal.
- Computer Use worked in Codex.
- ChatGPT selected its bundled native runtime.
Important attribution boundary
The following current configuration is not evidence that CodexSplit is still active:
[mcp_servers.computer-use]
command = "./Codex Computer Use.app/Contents/SharedSupport/SkyComputerUseClient.app/Contents/MacOS/SkyComputerUseClient"
args = ["mcp"]
cwd = "."
enabled = false
ChatGPT 26.803 writes this disabled compatibility block itself when using the node-repl Computer Use variant; the active local path is the enabled node_repl server. Restore Native should preserve ChatGPT-owned compatibility state rather than treating it as CodexSplit residue.
A separate ChatGPT Work-only failure was also observed after recovery: Work did not inject Computer Use and left the conversation turn spinning, while Codex Computer Use and Appshot both worked. That Work-only problem is being reported to OpenAI and is not included as a CodexSplit defect here.
Expected behavior
After Restore Native reports success:
- all CodexSplit-owned bridge processes and launch environment overrides are stopped/cleared;
- the currently running ChatGPT process is restarted, or the UI clearly requires a restart;
- official ChatGPT-owned node-repl/Computer Use configuration is preserved;
- Appshot and native Computer Use are tested end to end;
- the UI does not report success while ChatGPT still holds inherited bridge or Apple Events state.
Suggested fix
Add a restore completion health check:
- Stop the background gateway, not only the visible window.
- Clear CodexSplit-owned global and process-scoped runtime overrides.
- Detect whether ChatGPT is already running with inherited state.
- Prompt for or perform a ChatGPT restart.
- If the native integration returns
-1743, show a targeted Apple Events recovery action.
- Verify both Appshot capture and a native Computer Use connection before showing “restored”.
- Preserve official disabled compatibility entries used by ChatGPT's node-repl mode.
Regression test
Automate this sequence on a clean macOS account:
- Verify Appshot and Computer Use.
- Launch CodexSplit 2.0.0.
- Trigger Restore Native.
- Verify the background gateway is stopped.
- Verify the unified ChatGPT app is using its bundled Codex runtime.
- Verify Appshot returns screenshot + accessibility text.
- Verify native Computer Use can inspect a harmless app such as Calculator.
Summary
With CodexSplit 2.0.0 on macOS Apple Silicon, native ChatGPT Desktop Computer Use and
Cmd+CmdAppshot can remain unavailable after CodexSplit has been opened and the in-app Restore Native action reports completion.The native integrations recovered only after fully quitting both apps, resetting the affected Apple Events approval state, and relaunching ChatGPT. The current restore flow therefore does not provide an end-to-end guarantee that the already-running unified ChatGPT process has returned to a healthy native state.
This is a new-version follow-up and is intentionally separate from #32, which covered OpenCodex 1.2.0.
Environment
Reproduction
Cmd+CmdAppshot working in the unified ChatGPT Desktop app.Actual behavior
Restore Native did not immediately restore a usable native integration in the running ChatGPT process.
Appshot/Computer Use remained unavailable until manual recovery and an app restart.
The earlier failure path included:
Closing only the CodexSplit window is insufficient because the background gateway may continue running; a full quit is required.
Recovery that worked
Fully quit CodexSplit and ChatGPT.
Confirm that no CodexSplit/OpenCodex global
CODEX_CLI_PATHlaunch environment remains.Reset the affected Apple Events approval state:
Relaunch ChatGPT.
After this recovery:
Important attribution boundary
The following current configuration is not evidence that CodexSplit is still active:
ChatGPT 26.803 writes this disabled compatibility block itself when using the node-repl Computer Use variant; the active local path is the enabled
node_replserver. Restore Native should preserve ChatGPT-owned compatibility state rather than treating it as CodexSplit residue.A separate ChatGPT Work-only failure was also observed after recovery: Work did not inject Computer Use and left the conversation turn spinning, while Codex Computer Use and Appshot both worked. That Work-only problem is being reported to OpenAI and is not included as a CodexSplit defect here.
Expected behavior
After Restore Native reports success:
Suggested fix
Add a restore completion health check:
-1743, show a targeted Apple Events recovery action.Regression test
Automate this sequence on a clean macOS account: