It would be great to have the option to create unlimited layers (or at least significantly more than 6) within a profile. The current 6-layer limit can become quite restrictive when using the Creator Micro 2 Pro with many different applications. With AppSense/App Linking, it would be extremely useful to assign a dedicated layer to each application and have the device automatically switch to the correct layer when that application is active. I understand that the three LEDs may make it difficult to visually indicate a large number of different layers. However, this would not be an issue for me personally, since I rarely look at the LEDs and would use the device almost exclusively through App Linking / automatic application detection. I don't need to know which layer is currently active because the correct layer would be selected automatically based on the application I'm using. For example, I might want separate layers for Photoshop, Illustrator, Premiere Pro, After Effects, Blender, DaVinci Resolve, VS Code, Discord, Spotify, my browser, and many more. Even if there were no way to visually distinguish every layer through the LEDs, I would still strongly prefer having unlimited layers available in the software. Ideally, users could create as many layers as they need, with App Linking automatically selecting the appropriate layer based on the active application. This would make the Creator Micro 2 Pro much more flexible for power users who work with a large number of different applications.

ionqg-w27105 8 days ago

💡

Feature Request

Add Claude integration for the Creator Micro 2.

David Vazquez 14 days ago

💡

Feature Request

It would be great to have full control over the LEDs under the individual keys, including the ability to assign different colors to individual keys. For example, users could assign specific colors to certain functions so that important or frequently used actions visually stand out at a glance. Some possible use cases: Red for destructive actions Green for frequently used or active functions Blue for navigation controls Yellow for recording or special actions Different colors for different categories of shortcuts It would also be useful to have the option to turn individual key LEDs on or off independently, rather than having to use the same lighting behavior for all keys. This could make the Creator Micro 2 Pro much more intuitive to use, especially for complex workflows with lots of custom shortcuts. Being able to visually identify important functions immediately would be a huge quality-of-life improvement.

ionqg-w27105 8 days ago

💡

Feature Request

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 about 1 month ago

11

🐛

Bugs

It would be great to have an automatic sleep/standby mode for the Creator Micro 2 Pro. For example, users could set an adjustable timeout, such as 10 minutes, after which the device automatically enters standby if there has been no activity. Even better would be an option to automatically put the device into standby when the computer is shut down or goes to sleep. Ideally, this could include settings such as: Adjustable inactivity timeout (e.g. 5, 10, 15, 30 minutes) Automatically enter standby when the computer is shut down Automatically enter standby when the computer goes to sleep Wake up automatically when the computer becomes active again This would be especially useful for reducing unnecessary power consumption and would make the device feel more polished and integrated with the computer's power management.

ionqg-w27105 8 days ago

💡

Feature Request

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 23 days ago

4

💡

Feature Request

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 21 days ago

5

🐛

Bugs

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 29 days ago

10

💡

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 22 days ago

8

🐛

Bugs

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 29 days ago

3

💡

Feature Request

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 16 days ago

2

🐛

Bugs

Hi there, not sure who needs to hear about this, but since I performed the last firmware update, the keyboard is pretty much unusable. The Work Louder app no longer recognizes it and stays in a permanent “Retrieving keyboard data” loop, and the connection with Codex gets lost after a few hours, and I need to delete the device from bluetooth, restart codex and cross fingers it reconnects. WTF?

Jan Stevens 10 days ago

3

🐛

Bugs

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 about 1 month ago

7

💡

Feature Request

Sometimes Codex gets into a bad state so I need to exit Codex. When I bring Codex back up, it fails to connect to the Creator Micro V2, although the Creator Micro V2 part of the Codex UI states that it is repeatedly trying and failing to connect. The Input app also fails to connect to the Creator Micro V2 when this happens. I have to reboot my Mac to get everything cooperating again. I use the Creator V2 in wired mode at all times because I find the wireless mode to be unreliable. When it works it is great, I feel like I have to be very careful to not disturb the session to keep connectivity between the hardware and Codex alive.

Derek Whatley 11 days ago

5

🐛

Bugs

I can not connect my Nomad E to input. I have tried on a windows device and a mac device. One my windows I reinstalled input and are on 0.18.0.0. My nomad is on v0.6.0. I have tried a hard and soft reset. I have been using the board as a daily driver since I got it but have been having some input problems (key repeating input). I wanted to update it because of this and I got got a new micro. I kinda forgot about updating it so it might be out of date. Any help would be great!

Kenton 23 days ago

2

🐛

Bugs

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 23 days ago

2

🐛

Bugs

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 23 days ago

3

🐛

Bugs

If codex micro is connected via usb cable to a PC, and the PC sleeps, codex micro switches to bluetooth finding mode. Glowing, blinking and what have you — obviously noone can sleep in the room with codex. What should be done: if pc sleeps, codex that is connected via USB sleeps also. Why I don’t connect it via bluetooth? The fucker immediately wakes up my win 11 pc as soon as pc sleeps. But that is another bug. — How I fixed this for now: removed the battery alltogether. This way if PC sleeps, codex loses power → no glow.

Andrey Piskov 10 days ago

🐛

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 about 1 month 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 about 1 month ago

4

🐛

Bugs