{"slug": "openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light", "title": "OpenAI is turning Flipper’s BUSY Bar into a physical ChatGPT status light", "summary": "OpenAI's latest production desktop build (26.901.20858, build 7658) contains a hidden, disabled-by-default setting that would let its Codex agent control Flipper's BUSY Bar, a $219 LED desk display, according to a RuntimeWire investigation. The setting, named busy-bar-enabled, is described as 'Whether Codex controls a connected BUSY Bar' and is accompanied by a busy-bar.asar graphics package with animations for ready, pending, error, and disconnected states. OpenAI had not responded to requests for comment at publication time.", "body_md": "# OpenAI is turning Flipper’s BUSY Bar into a physical ChatGPT status light\n\n**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.**\n\nBy [Ryan Merket](/author/ryan-merket)\n· Published\n\n**RUNTIMEWIRE INVESTIGATION** — Scoop\n\nOriginal reporting by RuntimeWire, based on reverse engineering.\n\n## Why it matters\n\nOpenAI is extending Codex beyond the app window, using third-party desk hardware to make long-running agent work visible without another custom device.\n\n## Reporting record\n\n### Finding\n\nOpenAI’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.\n\n### How we verified\n\nMethods: reverse engineering.\n\nRuntimeWire 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.\n\nRuntimeWire 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.\n\nTested versions: ChatGPT/OpenAI desktop 26.901.20858 (build 7658).\n\n### Reproduction\n\nRuntimeWire partially reproduced the finding.\n\nReproduction 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\n\n### File hashes\n\n`sha256:09c7ef96b5d524fef9b76270de216cf6d661ffad4727680a9b9631d18795183d app.asar`\n\n`sha256:b7dbed1121abec0831a4f84f69554f4573b114c143699039508aeb10839e510c busy-bar.asar`\n\n### Company response\n\nRuntimeWire requested comment; the company had not responded by publication time.\n\nOpenAI has added first-party support for controlling Flipper's [BUSY Bar](https://busy.app/products/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.\n\nCode reviewed by RuntimeWire on September 3rd contains a hidden, disabled-by-default switch for controlling a connected BUSY Bar. The build also includes a dedicated `busy-bar.asar`\n\ngraphics package designed around the dimensions of the device's LED display, with agent-like pill animations and graphics for four states: ready, pending, error and disconnected.\n\nRuntimeWire recreated how the bundled animations would appear on the device using assets extracted from OpenAI's desktop application. The demonstration was produced by RuntimeWire and was not provided, published, or approved by OpenAI or Flipper Devices.\n\nThe integration remains behind the switch, making the production build evidence of active product work rather than a public launch. But the implementation is unusually complete for a stray reference. OpenAI has packaged separate visual assets for the main conditions a user would need to monitor while Codex works: whether a task is waiting, ready or broken, and whether ChatGPT can still reach the hardware. Those states turn the BUSY Bar device into an ambient agent monitor instead of a generic focus timer.\n\nThat is a narrow job, and a useful one. Coding agents can spend minutes working outside the user's immediate attention. A display mounted above a monitor can show when Codex has finished or hit an error without requiring the developer to keep ChatGPT in the foreground.\n\n### Flipper built the hardware for integrations\n\n[Pavel Zhovner](https://blog.flipper.net/author/zhovner/), the founder of Flipper Devices, has spent years building physical tools intended to be modified after they leave the factory. The BUSY Bar device carries that approach into productivity hardware.\n\nThe device has a 72-by-16 RGB LED matrix on the front, a 160-by-80 monochrome OLED on the back, physical controls and Wi-Fi, Bluetooth and USB connectivity. Flipper also exposes an HTTP API over a virtual USB network connection, allowing desktop software to render graphics and read device state locally.\n\nThat open interface gives OpenAI a relatively simple route onto a physical display without manufacturing another peripheral. The BUSY Bar's [developer tools](https://busy.app/pages/downloads) already support custom graphics, timers, audio and WebSocket state streams, with official Python and TypeScript libraries available for developers.\n\nOpenAI's code points to a native integration inside ChatGPT rather than a plugin that users must assemble themselves. The distinction matters because independent developers have already connected Codex to the same device. The novelty here is first-party OpenAI support, not the first pairing of Codex and BUSY Bar hardware.\n\nOne [open-source BUSY Bar controller](https://github.com/kylewhirl/busybar-codex) describes itself as a tactile Codex controller with live task status, navigation, reasoning controls and dictation. It mirrors Codex tasks and actions onto both displays, but depends on undocumented desktop internals and a local Chrome debugging connection. OpenAI's built-in implementation can tie the display to the app's own task state and connection handling, removing the bridge and its compatibility risks.\n\nThe outside project is more ambitious in one respect: it maps the BUSY Bar's buttons and dial to task selection, reasoning controls, approvals and voice input. The production ChatGPT assets reviewed by RuntimeWire establish status handling and device control, but do not establish that OpenAI will expose the full physical control surface.\n\n### OpenAI is building a hardware layer for agents\n\nThe BUSY Bar is the second desktop control surface connected to OpenAI's coding product. [Codex Micro](https://learn.chatgpt.com/docs/features/codex-micro), OpenAI's limited-run collaboration with keyboard maker Work Louder, connects to the ChatGPT desktop app over USB-C or Bluetooth. Its keys let users move between chats, use voice input and trigger actions such as approve, decline and continue in a new chat.\n\nThe two devices address different parts of the same problem. Codex Micro keeps agent controls under the user's hands. The BUSY Bar can make agent state visible across a room, including to someone who has stepped away while a task runs.\n\nSupporting existing hardware also gives OpenAI a lower-friction distribution path. Codex Micro is a purpose-built, limited-run accessory. The BUSY Bar is an independently sold device with an open API, a monitor mount and a screen designed to communicate status at a glance.\n\nThe four bundled states show the immediate scope of OpenAI's work. ChatGPT needs to discover the device, maintain a connection and translate Codex activity into simple visual conditions. Flipper supplies the screen and transport. OpenAI supplies the agent state.\n\nFor a company pushing Codex toward longer and increasingly autonomous assignments, that last step is becoming part of the interface. The agent no longer has to occupy the screen to demand the user's attention. A small light above it can handle that job.", "url": "https://wpnews.pro/news/openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light", "canonical_source": "https://runtimewire.com/article/openai-is-turning-flipper-s-busy-bar-into-a-physical-chatgpt-status-light", "published_at": "2026-09-03 07:40:54+00:00", "updated_at": "2026-09-03 07:53:42.020780+00:00", "lang": "en", "topics": ["ai-products", "ai-agents", "developer-tools"], "entities": ["OpenAI", "Codex", "Flipper", "BUSY Bar", "RuntimeWire"], "alternates": {"html": "https://wpnews.pro/news/openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light", "markdown": "https://wpnews.pro/news/openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light.md", "text": "https://wpnews.pro/news/openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light.txt", "jsonld": "https://wpnews.pro/news/openai-is-turning-flippers-busy-bar-into-a-physical-chatgpt-status-light.jsonld"}}