OpenWalkieTalkie 0.5.0 fixes the connection between Codex Desktop and your deck. It also adds firmware support for two alternative flash chips and packages full-chip images for factory programming.
Desktop tasks reach the shared service
The previous launcher could open Desktop successfully while leaving its conversations invisible to OpenWalkieTalkie. Desktop’s default plugin settings caused its implicit shared-service mode to fall back to a private server. The updated launcher selects the shared local connection explicitly.
Compatible installations named either ChatGPT.app or Codex.app are detected. The launcher reuses the existing Codex service and leaves running Desktop tasks alone. A separate fix restores replies from short tasks that finish before OpenWalkieTalkie subscribes to their conversation.
Repair the integration after updating
Install the 0.5.0 app and check that its service also reports 0.5.0. Open Integrations → Codex Desktop and install or repair the integration. When your Desktop tasks are idle, quit Codex Desktop / ChatGPT and open ~/Applications/Codex with OpenWalkieTalkie.app.
This is a small launcher for your installed Desktop app. Use it for future launches too: opening the original app directly does not enable the shared connection. Unsupported Desktop builds produce an error instead of silently opening a disconnected session.
More flash options and factory images
The firmware now accepts Puya PY25Q128HA-SUH-IR (C5354566) and GigaDevice GD25Q128ESIGR (C2928891), alongside the existing Winbond W25Q128JVSIQ (C97521). Its settings, pairing, and bootloader writers verify a stable supported chip ID before enabling writes. Boards populated with the alternative parts still need physical qualification.
The release includes a factory ZIP with separate 16 MiB images for Rev A and Rev B. Each combines the exact released application and recovery binaries with a fresh flash table and empty unit storage. Chinese instructions, component hashes, and a standalone verifier are included.
Factory images overwrite all flash contents, including settings and pairing data. They are for blank-board provisioning. Existing devices should use the app’s normal USB updater.
Updating an existing deck
Connect one deck over USB-C and open Service → Updates → Check firmware. The partition layout and recovery protocol are unchanged from 0.4.0, so devices already on recovery protocol 2 receive a normal application update.
Devices still on the old bootloader need the guided migration. Keep power connected and the Mac awake: losing power during bootloader replacement can prevent startup and USB recovery and require hardware repair. The app displays this warning before migration. Do not manually install bootstrap or recovery files as application firmware.
What we verified
The launcher and transport regression tests pass. In a live test on the development Mac, Desktop connected to the shared service and its DESKTOP-LINK-OK reply appeared in the OpenWalkieTalkie GUI. USB delivery to the connected Rev A was healthy; the final physical screen check was not recorded.
Both board variants pass software checks. The preceding 0.4.1 development firmware with the same flash support completed an old-bootloader migration on the existing Rev A. The CI-built 0.5.0 files were not flashed in that test. A shipped Rev B, boards with the alternate chips, and blank-board factory programming still need hardware validation. No device audio test was performed.
Get v0.5.0
Use Check for Updates or download the signed and notarized Mac app for Apple Silicon or Intel. macOS 13 or later is required.
The GitHub release includes firmware, factory images, checksums, build attestations, and a Chinese upgrade guide. The guide is also included in each DMG.