OpenAI is turning Flipper’s BUSY Bar into a physical ChatGPT status light
RuntimeWire found a hidden, disabled-by-default BUSY Bar control in the latest desktop build, plus a dedicated animation package for task, ready, pending, error and disconnected states.
By Ryan Merket · Published
RUNTIMEWIRE INVESTIGATION — Scoop
Original reporting by RuntimeWire, based on reverse engineering.
Why it matters
OpenAI is extending Codex beyond the app window, using third-party desk hardware to make long-running agent work visible without another custom device.
Reporting record
Finding
OpenAI’s latest production desktop build contains a hidden, disabled-by-default setting allowing Codex to control a connected BUSY Bar, accompanied by a dedicated graphics package containing animations and device-status states sized for the BUSY Bar display.
How we verified
Methods: reverse engineering.
RuntimeWire found a new hidden preference in OpenAI desktop build 26.901.20858 (build 7658) named busy-bar-enabled. Its internal description reads: “Whether Codex controls a connected BUSY Bar.” The setting is marked hidden and defaults to false.
RuntimeWire compared OpenAI desktop application packages from builds 7119 and 7658, searched application code for new device-specific preferences, and isolated the new busy-bar-enabled configuration. We separately inspected the accompanying busy-bar.asar resource package, extracted its animation assets, reverse-engineered the bicycle0 animation container sufficiently to reconstruct the original display frames, and checked the resulting dimensions and timing against BUSY Bar’s published hardware specifications.
We also searched OpenAI’s public documentation and current public reports for an announced first-party BUSY Bar integration. We found existing third-party Codex integrations, but no OpenAI announcement or documentation for the first-party implementation described above.
Tested versions:
- ChatGPT/OpenAI desktop 26.901.20858 (build 7658)
Reproduction
RuntimeWire partially reproduced the finding.
Reproduction instructions Obtain OpenAI desktop version 26.901.20858 / build 7658. Inspect the packaged Electron application code. Search for the exact string: Whether Codex controls a connected BUSY Bar The corresponding preference is: busy-bar-enabled Verify that it is configured with: agentAccess: hidden default: false Inspect the application resources for busy-bar.asar. Extract the archive and verify the numbered pill and status animation assets. Decode the .anim files. The resulting display frames are 70×16 pixels. Repeat the preference search against 26.820.60940 / build 7119. The BUSY Bar preference and exact description are absent from that baseline. Our exact baseline searches returned no match for busy-bar-enabled, the internal description, or busy-bar
File hashes
sha256:09c7ef96b5d524fef9b76270de216cf6d661ffad4727680a9b9631d18795183d app.asarsha256:b7dbed1121abec0831a4f84f69554f4573b114c143699039508aeb10839e510c busy-bar.asar
Company response
RuntimeWire requested comment; the company had not responded by publication time.
OpenAI has added first-party support for controlling Flipper's BUSY Bar to a production version of the ChatGPT desktop app, giving ChatGPT's Codex a direct line to the $219 LED display sitting on a user's desk.…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.