Environment: macOS Codex Micro Work Louder Input 0.17.1 Device firmware v0.4.1 ChatGPT desktop app with Codex integration Issue: ChatGPT takes global control of the Codex Micro underglow and overrides the lighting configured for non-Codex layers. Steps to reproduce: In Input, configure Layer 2 with custom key backlighting and underglow at nonzero brightness. Completely quit ChatGPT. Switch to Layer 2. Both the key LEDs and underglow work correctly. Open ChatGPT. Switch between the Codex layer and Layer 2. Actual behavior: Opening ChatGPT overrides the device lighting. On Layer 2, the configured key LEDs can still illuminate, but its configured underglow remains off. Quitting ChatGPT restores the Layer 2 underglow. The issue reproduces in both directions regardless of which layer is active when ChatGPT launches. Expected behavior: ChatGPT should control Codex status lighting only while the Codex layer is active. On Layers 2–6, firmware should release RGB control and apply that layer's backlight and underglow settings from Input. Diagnostics: Input successfully saves the Layer 2 lighting configuration. Input logs show successful lights.preview and fs.writebin calls. After ChatGPT opens, the logs show Codex-specific v.oai.rgbcfg commands. The hardware and LEDs are confirmed working because all configured lighting operates normally when ChatGPT is closed. This appears to be a lighting-ownership conflict between ChatGPT's Codex integration and the per-layer Input configuration.

Zandre Azogue 18 days ago

11

🐛

Bugs

I’m having an issue with Creator Micro 2 native Codex integration. The device works as a normal HID/input device, but the Codex-specific controls do not activate. Summary: Device: Creator Micro 2 Firmware: v0.6.1 Firmware source checked: latest Work Louder cm-v2-fw-releases release is v0.6.1 Input app: 0.18.0 ChatGPT/Codex app: 26.727.51351 macOS USB VID/PID: 0x303a / 0x8298 Connection: USB-C wired Device appears in macOS hidutil list as Creator Micro 2 Expected behavior: Long-pressing the dial in Codex should open the Codex Micro configuration panel. The dial should adjust Codex reasoning level. Voice / push-to-talk and Codex-specific mappings should work. Actual behavior: Normal key/HID behavior works. Codex native controls do not work. Long-pressing the dial does not open the Codex configuration panel. Reasoning level and voice mode controls do not activate. Troubleshooting already completed: Updated Creator Micro 2 firmware to v0.6.1. Confirmed v0.6.1 is the latest published Creator Micro 2 firmware. Reset/deleted the Input profile from Input.app. Quit Input.app completely. Quit Chrome completely. Restarted the Mac. Reconnected the Micro by USB before opening other apps. Confirmed no obvious keyboard utilities were running: Input.app not running Chrome not running Karabiner not running Logitech Options not running BetterTouchTool not running Keyboard Maestro not running Relevant macOS / app log evidence: Codex/Input successfully read the device firmware: {"result":{"version":"v0.6.1"},"id":389,"method":"sys.version"} Device status was also readable: {"result":{"version":"v0.6.1","profile_index":0,"layer_index":1,"battery":100,"is_charging":true},"id":415,"method":"device.status"} But when ChatGPT/Codex attempts native device access, macOS logs: ChatGPT@(null): AppleUSBHostUserClient::openGated: failed to open Creator Micro 2@00100000: provider is already opened for exclusive access by AppleUSBHostCompositeDevice The device then continues to enumerate normally as: AppleUserHIDDeviceManufacturer: Work LouderProduct: Creator Micro 2VendorID: 12346ProductID: 33432PrimaryUsagePage: 1PrimaryUsage: 6 My read: The device is visible and responding over HID/RPC, and firmware is current. The failure appears to be in the native Codex control handshake or device-claim path, not in the Input profile or firmware update state. Can you confirm whether this is a known issue with Creator Micro 2 firmware v0.6.1 and ChatGPT/Codex app 26.727.51351 on macOS? If there is a beta firmware/app build, permission setting, or reset sequence needed for the Codex native mode, please send the exact steps.

Matt 8 days ago

3

💡

Feature Request

Hi Work Louder team, I've just ordered a Creator Micro 2 Pro. Before it arrives I'd like to check what's possible on the host side, so I build the right thing rather than guess. I'm writing a small local macOS app for my own use that supervises coding-agent sessions - conceptually the same job the Codex Micro does for Codex, but for a different tool and running entirely on my own machine. Mapping keys to actions is straightforward with Input. What I'd like to know is whether the feedback direction is available to me: lighting individual keys from my own app to show live status, the way the Agent Keys work on the Codex Micro. Three specific questions: Does the Creator Micro 2 expose a raw HID interface (QMK-style usage page 0xFF60, or any vendor-specific interface) that a third-party host application can open and write to? Is there a supported or permitted way to set per-key RGB from a host app — an Input API, a documented report format, a local socket, anything? I understand the Codex integration is a specific partnership; I'm asking about the general capability, not access to that integration. If nothing exists today, is it something you'd consider? A documented "set key N to colour X" channel would make the Micro the obvious controller for any agent-style tool, not only Codex — that seems like it's in your interest as much as mine. Also useful to know, if you can say: is the Creator Micro 2 firmware QMK/VIA-based like the original Creator Micro, or a different stack? I noticed the v2 isn't in QMK mainline, so I don't want to assume. Happy to be pointed at docs if these are already answered somewhere — I couldn't find them. Thanks, Paulo

Paulo Ribeiro 14 days ago

6

💡

Feature Request

Homebrew is a popular package manager used by many Mac OS users and developers. Having input as a Homebrew cask would make it a lot easier to install and update for those of us who use the program. Would the team consider adding input to Homebrew?

nejm 14 days ago

1

💡

Feature Request

Does the standard Creator Micro 2 get detected by the ChatGPT desktop app as a Codex Micro and support Agent Keys with live RGB chat status, push-to-talk and Codex settings without Work Louder Input? (or can be used in the same fashion)

PeterP 16 days ago

6

💡

Feature Request

Input Version 0.18.0 (0.18.0) MacOS Tahoe 26.2 Did both a manual reset on the board itself and multiple power cycles / modes. Nothing seems to get it to escape out of this state

Evan 7 days ago

5

🐛

Bugs

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.

tfraley 15 days ago

4

🐛

Bugs

I’m unable to connect a Work Louder Creator Micro 2 to Codex in the ChatGPT macOS app. Environment Device: Creator Micro 2 Firmware: v0.4.0 USB VID/PID: 303A:8298 ChatGPT/Codex: 26.721.41059 (build 5848) Work Louder Input: 0.17.2 Connection tested: Bluetooth and direct USB-C Steps to reproduce Connect the Creator Micro 2 over Bluetooth or USB-C. Ensure Work Louder Input is closed. Open or restart ChatGPT/Codex. Wait for Codex to detect and initialize the device. Expected result Codex connects to the Creator Micro 2 and enables its controls and agent-status lighting. Actual result Codex detects the device but repeatedly reports a connection problem. Diagnostics show: v.oai.thstatus → RPC 404 “Method not found” Codex Micro control-plane initialization failed The v.oai.rgbcfg command succeeds, indicating that Codex can communicate with the device. The failure occurs over both Bluetooth and USB. Troubleshooting completed Restarted macOS and ChatGPT/Codex. Tested Bluetooth and direct USB-C connections. Confirmed macOS recognizes the device as a USB/Bluetooth HID. Quit Work Louder Input completely. Confirmed Input reports firmware v0.4.0 as current. Confirmed no common keyboard remapper or security utility is claiming the device. The Creator Micro 2 is advertised as directly integrated with Codex, so this appears to be a compatibility mismatch between Codex and the current Creator Micro 2 firmware.

Ansh 15 days ago

4

🐛

Bugs

I’m using a Creator Micro V2 with Work Louder Input 18.0 and firmware 0.6.1 on a Mac running macOS Golden Gate 27. Bluetooth has been extremely unreliable. When the Creator Micro goes to sleep, it often fails to reconnect properly after waking. Restoring the connection can take 15–20 minutes of restarting the device, forgetting it in macOS, and pairing it again. Each successful re-pairing also appears as another Bluetooth device. I now have five or six duplicate Creator Micro entries. Even after turning the device off and choosing “Forget This Device,” the old entries continue to appear under Nearby Devices. I originally assumed this was caused by the beta software or firmware, but the problem remains after moving to the full Input 18.0 release with firmware 0.6.1. Expected behavior: The Creator Micro should reliably reconnect to the same Bluetooth pairing after waking from sleep. Actual behavior: It frequently fails to reconnect, requires extensive troubleshooting and re-pairing, and creates duplicate Bluetooth entries. At this point, the Bluetooth experience is frustrating enough that the device doesn’t feel dependable for daily use.

tfraley 6 days ago

🐛

Bugs

Riffing off some issues: - the agent keys at the top don't care about "normal chat" windows - i can't switch between chat / work / codex using the nipple or the knob - i should be able to clear the current prompt with a button or swipe of the nipple if i make a mistake in the composer input, i thought the point was not to have to use the keyboard - i should be able to submit a prompt for a "normal" Chat (note: not a work / codex conversation) using the "Send message" – instead I get "This action is not available here", wtf! - if i can't edit the Codex layer in the Input app, why can't I carry across the special shortcuts from the codex layer to a new custom layer? and vice versa, why can't I add custom shortcuts to the codex layer? - i should be able to disable bluetooth or turn off the pairing mode function on the touch sensor, i've been switching layers and it's way too sensitive - going to ultra reasoning triggers the new warning about full access - either allow me to acknowledge this once, or give me a shortcut to accept - making a new layer, switching to it on the codex micro using the touch sensor, and deleting the layer on Input seems to leave me on the deleted layer - i can't get live agent status keys to work on a custom layer? get outta here! - give me something useful like a quick way to toggle usage limits and context usage % - maybe give me the option to use the knob contextually to dismiss popups like the full access warning - maybe just give me access and i can make it useful myself thought it’d be more customizable than this, can i get a refund?

sam_altman_2 17 days ago

1

💡

Feature Request

Environment: Creator Micro V2 / Input 0.18.0 / firmware flashed 0.4.0 to 0.6.1 / macOS over Bluetooth, also seen on Windows 11. A single physical key press registers as two or more presses. It affects every key, not one switch. THE DECISIVE TEST: after the problem survived the firmware update, I ran a full “Reset settings” from the Setup tab, leaving the device factory-blank (no custom layers, no macros, no Multi keys). I then assigned a single plain letter A to one key via Basic, opened a plain text editor, and tapped it slowly ten times. I still get doubled characters (aa) from single presses. That rules out everything on my end: not my keymap (device was wiped), not Multi-key logic (none existed), not macro complexity (a single unmodified keystroke). TIMING DETAIL: before the reset I built a Multi key to characterise it (tap types 1, double-tap types 2, hold types 3). One quick tap: expected 1, got 1 or 2 - Deliberate double-tap: expected 2, got 2, 22, or 21 - Hold ~1 second: expected 3, sometimes got 31 A single tap yielding 2 means one press bounces into two contacts inside the 250ms tap window. Hold yielding 31 means the RELEASE bounces too: the hold fires, then letting go registers as a fresh tap. So the board chatters on both make and break. This also corrupts ordinary single-action keys, not just Multi keys. A Delete key can remove two items from one press, which makes the pad risky to use in Outlook. ALSO: since flashing 0.6.1, the Firmware version field in Setup displays blank. Device model and Input version populate normally. It read 0.4.0 before the update. Possibly unrelated, possibly a sign the flash did not complete cleanly. I saw the report here about a corrupted keymap.json surviving a firmware update and producing repeated key input (“endless K”). Mine looked similar, which is why I tried the reset, but the reset did not resolve it. QUESTIONS: Is this known on this hardware revision or firmware line? 2. Is there a debounce / tapping-term setting, or a firmware build with a longer debounce window? 3. Should the Firmware version field be blank after a successful 0.6.1 flash? 4. If this is a hardware fault, what is the warranty process? Happy to run any diagnostic or reflash. My profile is exported, so wiping the device again costs me nothing.

CrockDaddyFlex 8 days ago

1

🐛

Bugs

Hi, I received my Codex Micro today and haven’t been able to use it at all. On the very first connection attempt, Input showed “No Device Found.” I’ve tried multiple known-good USB-C data cables and tested the keyboard on two different Macs, but the result is the same. The device doesn’t appear in macOS System Information, system_profiler SPUSBDataType, or ioreg -p IOUSB, even when connected directly to the Mac. Other USB-C devices work normally with the same ports and cables. Since the keyboard has never successfully connected or been used, this appears to be a defective unit. Could you please arrange a replacement? If you could share a support email address (or open a support ticket), I'd be happy to send my order number, screenshots, terminal output, and a video of the issue there. Thanks!

Morgan Lim 9 days ago

1

🐛

Bugs

I’m having a recurrent connection problem with the Codex Micro after my Mac wakes from sleep. What happens: Before sleep, the Micro works normally over Bluetooth. After the Mac has been asleep overnight, I tap the Micro to wake it. It flashes blue. Layers 2 and 3 still work normally Codex layer 1 does not work. The Agent Keys, dial, and other Codex controls do nothing, and ChatGPT does not reconnect to the device. Fully quitting and reopening ChatGPT immediately fixes the problem. I do not need to re-pair Bluetooth or restart the Micro. This has happened more than once. It makes the Codex layer unreliable because I have to restart ChatGPT after the computer sleeps.

Brian Pridgen about 19 hours ago

🐛

Bugs

After being connected for a little while, the Codex Micro will wind up effectively frozen: The indicator caps will display a stale state Key presses on any key will not result in any change or action on the computer The Codex app will continue to indicate that the device is connected I have to turn the device off, wait several minutes, and turn it back on in order to resolve the issue. This happens every half hour or so, but intermittently. It does better during periods of continuous use than if it’s left idle for 20-30 minutes.

Corey Ward 17 days ago

1

🐛

Bugs

Just got the codex micro. Input 0.17.2. Mac OS 26.0.1 (25A362)

dante 17 days ago

💡

Feature Request

Description I’m using a Codex Micro with the ChatGPT desktop app on macOS. Environment ChatGPT app version: 26.715.72359 (build 5718) Codex Micro: Connected Input Monitoring: Granted Microphone permission for ChatGPT: Enabled Selected microphone: Elgato Wave:3 Mic key action: Push to talk Expected behavior Holding the Mic key should start recording and show the sea-green lighting animation. Double-tapping should keep recording. Actual behavior Holding or double-tapping the Mic key does nothing. Recording does not start, and there is no lighting change. Troubleshooting completed Confirmed the Elgato Wave:3 works and shows input activity in macOS. Selected the Wave:3 under ChatGPT Settings → Voice → Microphone. Confirmed ChatGPT has macOS microphone permission. Confirmed Codex Micro Input Monitoring is granted. Confirmed the device is connected and other Codex Micro keys work. Configured ChatGPT’s Toggle Dictation shortcut; dictation works through that shortcut. Confirmed the Mic key is assigned to Push to talk. Remapped the same physical Mic key to another action; that action worked. This confirms the physical switch and key event are functional. Restored the Mic key to Push to talk, but it still produces no response or lighting change. This appears specific to the Codex Micro Push to talk action rather than the microphone, permissions, connection, or physical key

GOAT 18 days ago

1

🐛

Bugs

After update to 0.4.0 Walpaper widget is not displayed.

Taras Rudyi 4 days ago

🐛

Bugs

The Codex Micro just doesnt work with either the Input app nor the ChatGPT right now. I’m on macOS. I have not been able to use it since I opened it. It worked for a short period, maybe 5 minutes, until I got to the stage where nothing works. It does connect to ChatGPT sometimes I think? But no inputs are registered at all.

Tony Jin 13 days ago

1

💡

Feature Request

Creator Micro 2 LED Color broken? Hey I have just received my Creator Micro 2 and am successfully using it with the MX Pure Keycaps for Codex. I have noticed that some colors and especially White have a two tone split on the left and right with the LED on the inside of the switch. White for example has a very clear blue on the left and green on the right (side differs per row seems like) and doesn’t look like White at all. Some colors have the same tone on the left and right while some exhibit the same behavior with White being the most drastic. It looks horrible and nothing like the Images on the website or Videos of the Creator Micro 2. The look of the White is unbearable, there is no way this is intended. I tested it on my Mac and on Linux, in Codex and by manually setting the color. Both suffer from the same issue. I’m on the latest 0.6.1 firmware. - Pictures for reference - Bad ones: “White" (blue one one side, green on the other): Light blue (light blue/teal on one, dark blue on the other): Yellow (lime on one, yellow/orange on the other): Lime (green on one, light blue on the oth

maad Tech 8 days ago

🐛

Bugs

I'd like to be able to edit the agentic layer in the Input app just like the other layers. Could we have the keys KV_OAI_AG00..KV_OAI_AG05, KV_OAI_ACT00..ACT20, KV_OAI_ENC_CC / CW/ CLK available in the key list under a new category "Agentic"? If not for everybody, behind an "Advanced" flag? This roadblock feels unnecessary:

Okko Ojala 8 days ago

💡

Feature Request