I use an XYZ Work Board r2 with firmware v0.1.2 (the latest release) and Input 1.0.2. I want to turn single key LEDs on and off and set their colour. For example: show which keys have a macro, show a status from an app on my computer, or light the keys that are active in the current layer. Today I can only set the backlight and the underglow as two whole zones. I cannot set the colour of one key. The Creator Micro 2 and Codex Micro firmware can already light single keys from the computer. Could you add the same feature to the XYZ firmware? What would help me most: a way to set one key, or a list of keys, to a colour or to off (in Input per layer, and from my computer with a small public command); a way to give lighting control back to my layer settings; and short documentation for this command, kept stable so I can build on it. Related posts: “Per-Key LED Color Control” and “Can a third-party app drive per-key RGB on the Creator Micro 2?”. Both are only about the Creator Micro 2. I am happy to test a beta firmware on my XYZ. Thank you!
Hi, would it be possible to get the 80 × 30 cm mat in a combination of green and grey instead of black, using the colours you currently offer? In my opinion, black absorbs too much light, making it difficult to find small items on the mat. Thanks!
On Input I can assign a backlight color/behaviour and and underglow color/behaviour on the fp layer, but it does not light up in the product. When I click or hold the fp key the lights do not change. The lights change with no problem on the other layers. XYZ Workboard r2 firmware 0.1.2, input app 1.0.2, Win 11
I don’t want to break anything; it’d be great to have some brief instructions or a video. https://worklouder.cc/wrk-mx-pure
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.
Hi! I'm having an issue with my Work Louder × Framer 2025 device, which stopped working after I hadn't used it for a while. Initially, the device was not being detected by the Input software. Now, the problem has gotten worse: the device lights up when connected via USB, but none of the buttons work at all. Here is what I've tried and observed so far: -The device lights up when connected via USB. -None of the buttons register any input, even when Input is completely closed. -Nothing happens when I press the buttons in Windows Notepad. -Windows Device Manager does not appear to detect the device when I plug it in or unplug it. -I suspect there may be an issue with the USB connection, firmware, or the device itself, but I'm not sure what is causing it. Could you please advise me on the next steps to diagnose and fix the problem? Best regards //Alex
would be great to have stock profile or layer definitions for common OS commands that typically require chords.
My Knob1 is not responsive after I tried updating it. The update kept failing. Now when I try to flash or update it it’s stuff at “0% update in progress”. Any solutions for this? Thank you.
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.
Also, it enters on Bluetooth with a different device ID, requiring a new pairing / connection instead of automatically connecting if previously connected. This is really bad.
Hello - I purchased one of the original ‘clicky’ codex mini keyboards from OpenAI supply. I’m not really sure how exactly it happen but I carry it in a brief case with my MacBook when traveling, and this last time doing that proved too much for dial-knob, and it’s now busted off. Anyway, I’m just hoping now to get the correct part number so I can take for repair here locally in Silicon Valley. Also, I don’t want to take this time to complain irrately but this is probably useful feedback…As I gathering up the pieces to inspect I noticed the rotary encoder shaft was so cheap that it made the heavy weight of the HID as a whole seem deceptive, at least a quality indicator—the metal housing cap sliced right through notch meant for seating the encoder shaft, that break what provided the give to bend the shaft ring of the cap.
It would be great if the dock icon can be hidden and instead it show in the menu bar.
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.
It would be very helpful to have a full preview of the codex layer, as the native view app does not show any information about the keys and prevents me from using multiple layers.
On Windows 11, when Creator Micro 2 Base is connected and Codex Desktop is running, the display never turns off and Windows never enters automatic sleep. I traced this to the Creator Micro 2 vendor HID interface: VID 303A / PID 8297 Usage Page FF00 / Usage 0001 Firmware 0.6.2 About every 60 seconds, Codex appears to request device.status. Creator Micro 2 replies with three HID input reports, and those reports reset Windows GetLastInputInfo() to approximately zero. The HID payload decodes to a device.status response. { "result": { "version": "0.6.2", "profile_index": 0, "layer_index": 1, "battery": 0, "is_charging": false }, "id": 289, "method": "device.status" } powercfg /requests shows no active requests. Closing Codex immediately stops the periodic HID traffic, and Windows idle/display sleep works normally again.
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
Allowing the ability to take fp to be dual binded for both globe and fn options. Not certain of the technical limitations if any to perform this addition. But this would be super cool to be able to open the Emoji window from a knob via input.