Creator Micro 2 Codex compatibility needs clarification and graceful fallback

I’m requesting clarification and a fix for the Creator Micro 2’s behavior with the ChatGPT desktop app’s Codex integration.

ENVIRONMENT

• Device: Creator Micro 2 Pro

• Firmware: v0.4.0

• Work Louder Input: 0.17.2

• ChatGPT/Codex: 26.721.41059 (build 5848)

• Platform: macOS

• Connections tested: Bluetooth and direct USB-C

WHAT HAPPENS

Codex detects the Creator Micro 2 and begins initializing it as a Codex-compatible device.

v.oai.rgbcfg succeeds

v.oai.thstatus RPC 404 “Method not found”

After v.oai.thstatus fails, Codex reports a connection problem, disconnects its HID session, reconnects, and repeats the loop.

The Creator Micro 2 otherwise works normally as a keyboard/macropad. Work Louder Input and macOS both recognize it, and the problem occurs over Bluetooth and USB.

TROUBLESHOOTING COMPLETED

• Restarted macOS and ChatGPT

• Tested Bluetooth and direct USB-C

• Completely quit Work Louder Input

• Confirmed Input reports v0.4.0 as current

• Confirmed the device works normally as a keyboard/macropad

• Confirmed Codex can communicate with it because RGB configuration succeeds

• Checked for common keyboard remappers and security utilities

• Reproduced the same missing-method response consistently

LIVE VIDEO

We encountered the compatibility problem during a live Creator Micro 2 unboxing and setup:

https://youtube.com/live/NBBaNMBGij8?feature=share

RELATED REPORTS ON THIS PORTAL

• Exact RPC 404 report:

https://feedback.worklouder.cc/p/creator-micro-2-fails-codex-initialization-voaithstatus-returns-rpc-404

• Creator Micro 2/Codex compatibility question:

https://feedback.worklouder.cc/p/is-creator-micro-2-also-detected-by-codex-chatgpt-app

• Codex Micro v0.4.1 HID/RPC stalls:

https://feedback.worklouder.cc/p/critical-codex-micro-v041-hidrpc-stalls-116-disconnects-in-2

• Codex Micro RGB ownership issue:

https://feedback.worklouder.cc/p/codex-micro-chatgpt-overrides-underglow-on-non-codex-layers

• Separate/incompatible firmware concern:

https://feedback.worklouder.cc/p/input-can-flash-incompatible-firmware-onto-codex-micro-without-warning

WHY THIS APPEARS TO BE A GENUINE INTEGRATION ISSUE

There seem to be two reasonable intended behaviors:

1. If Creator Micro 2 is supported with limited functionality, Codex should detect its capabilities, enable only supported controls, and clearly identify unavailable Codex Micro features.

2. If Creator Micro 2 is unsupported, Codex should identify it as unsupported and avoid attempting full Codex Micro initialization.

The current behavior is neither: Codex detects the device, successfully sends a Codex-specific RGB command, requires an unavailable endpoint, and enters an endless reconnect loop.

QUESTIONS FOR WORK LOUDER

1. Is Creator Micro 2 officially supported by the ChatGPT desktop app’s Codex integration?

2. 2. If supported, which Creator Micro 2 firmware implements v.oai.thstatus?

3. 3. Is v0.4.0 the correct firmware, or is another supported build required?

4. 4. If support is limited, which Codex features should work?

5. 5. If unsupported, why does Codex detect it, configure RGB, and begin Codex Micro initialization?

6. 6. Are Creator Micro 2 and Codex Micro on different firmware branches with different OpenAI RPC capabilities?

7. 7. Is a Creator Micro 2 firmware update planned?

8. 8. Could Codex negotiate device capabilities so a missing optional endpoint produces limited functionality instead of a reconnect loop?

SUPPORT CONTACT

I have already emailed Work Louder support with the device information and diagnostic evidence and am waiting for an official response.

REQUESTED RESOLUTION

• A supported Creator Micro 2 firmware update implementing the required Codex endpoints

• Confirmation of the minimum supported firmware and installation instructions

• Limited-functionality support with clear capability reporting

• An explicit unsupported-device message instead of repeated reconnection

• An official compatibility matrix for Creator Micro 2 and Codex Micro

I’m happy to provide additional logs or test a supported beta firmware. I do not want to install firmware intended for another Work Louder product.