Skip to main content

Have something to say?

This board helps us understand what actually matters to you, what improves your workflow, what slows you down, and what you’d love to see next. 💡 Upvote what matters to you!

Tell us what would make our gear more useful in your daily setup. Your feedback directly shapes what we build and what we’ll prioritize. 💜

‼️ Important: If you have multiple ideas, suggestions, or bug reports, please create a separate post for each one so we can track and address them individually.

Planned

XYZ Work Board r2: per-key LED control from the computer

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!

1
In Progress

Anthropic Claude - Creator Micro 2

Add Claude integration for the Creator Micro 2.

David Vazquez3 months ago
6

Bluetooth Multi-point Connection

It would be nice if we could connect with at least one more device. So we can use some sort of layer button to switch between the devices and have agent management rgb control on both. Or inside the same layer if we could devide the RGB buttons between multiple devices that would be sick as well!

Lucas Magalhães13 days ago

Green/Grey colour option for wrk. Mat

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!

isnone.24 days ago

How to replace key caps?

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

Michael Smith29 days ago

Per-Key LED Color Control

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-w271053 months ago
2

OS Desktop

would be great to have stock profile or layer definitions for common OS commands that typically require chords.

brian payne1 month ago
1

Unlimited Layers for Unlimited Programs

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-w271053 months ago
2

Hide Icon in Dock

It would be great if the dock icon can be hidden and instead it show in the menu bar.

Efren Gort Jr2 months ago
In Progress

Auto Sleep / Standby Mode

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-w271053 months ago
2

Preview for Codex Layer

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.

Maksym Mykhailenko2 months ago
In Progress

Can a third-party app drive per-key RGB on the Creator Micro 2?

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 Ribeiro4 months ago
13

Adding the GLOBE key from Mac as a bindable option

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.

Kaleb Moody2 months ago
1

OpenChamber integration

Please provide an integration with OpenChamber. Alternatively, your input app should be able to define bindings for OpenChamber including dynamic agent-buttons, like the Codex-Integration provides for Codex Micro.

Kai H. Meder2 months ago

Input’s Dock icon repeatedly bounces while the application remains running

Input’s Dock icon repeatedly bounces while the application remains running I’m seeing repeated bouncing of the Input icon in the macOS Dock. Visually, it looks like the app or a background component is constantly restarting. Process inspection, however, shows that the main application stays running. Environment: Input: 1.0.0-rc.7 macOS beta: 27.2, build 26B5091g Device: Creator Micro 2 Firmware: 0.6.3-rc.16 Bundled Electron: 40.10.6 Observed behavior: The main Input process and its four Electron helper processes had been running continuously for over 17 minutes. During a 25-second observation sampled approximately every 200 ms, their process IDs remained unchanged. In that same period, 19 separate short-lived osascript processes were observed as children of Input, approximately one every 1.3 seconds. These processes execute: /Applications/input.app/Contents/Resources/scripts/window-info-retriever.scpt Inspection of the installed application’s JavaScript shows that the AppSense/focused-app service repeatedly calls this script to identify the active application. After each call completes, it schedules the next call with a 1,000 ms delay. This appears to be intentional polling, rather than a crash/restart loop. The potentially relevant finding is how macOS registers these short-lived processes. Launch Services logs show each osascript process checking in under Input’s bundle identifier, it.focusense.input-app. RunningBoard then assigns it a foreground application assertion. For example: launchservicesd: CHECKIN:0x0-0x6c56c5 7738 it.focusense.input-app runningboardd: Acquiring assertion targeting [anon (501):7738] "foregroundApp:7738" runningboardd: [anon (501):7738] Set darwin role to: UserInteractiveNonFocal That process exits shortly afterward, and the sequence repeats with another PID. My working hypothesis is that these repeated foreground registrations under Input’s identity trigger the Dock animation, making normal AppSense polling look like repeated application launches. The process lifecycle and registrations are confirmed by local observation. The connection to the visible Dock animation is a strong hypothesis, but it has not yet been confirmed through an A/B test with the polling disabled. I also cannot establish whether this is a regression specific to the macOS beta. Expected behavior: AppSense should detect the active application without repeatedly animating Input’s Dock icon or registering each short-lived helper as a foreground application. Could you investigate how the AppSense AppleScript process receives its application identity and foreground status on this macOS build? A background-only helper or a persistent native mechanism for observing active-application changes may avoid this behavior.

Oleksandr Diudiun2 months ago
1

Creator micro V2 poor wireless connection

When ever i’m try to connect my Creator micro it’s always forget my device and can’t connect to the input and even I can connect it just forget all my device data or shortcut that I have setting, by the way my Macro is on the latest version i’m also trying everything that Recommended by Work louder and it still the same. I know that this company isn’t big but i’m have seen a lot of this product promote around also promise to save time and make life easier but in reality in doesn’t help me anything, i’m also have a lot of work to do but I just waste my time setting and reset everything over and over again.

Rain Zaza2 months ago

Herdr Integration

The Creator Micro 2 is an amazing macro pad, and I think it will have a lot of interest now and in the future. You've definitely got a customer for life. That said, there are many different applications we could potentially use. One of the biggest use cases I've/you’ve seen is AI‑assisted development, especially since you also released the Codex Micro. A variety of tools are already in use, and I’d like you to consider opening an option for people to develop presets for you. I frequently use more than one agent to help complete work, and Herdr is one of the applications that facilitates this. There are options out there already, but it interferes with the Input application itself. Could we get Herdr integration and, then, potentially support for individual key lighting, such as the following? https://github.com/schacon/micro-manager

Todd Wardzinski3 months ago
3

Creator Micro 2 STILL not activating Codex native controls on macOS

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.

Matt4 months ago
4

Disable Layers / Add individual key light controls and effects

I have accidentally hit the layer switch at least 10 times and would love a way to turn it off at this time I am only using one layer and really dont see myself going to any additional layers I would also love if you would make each key have individual light controls and effects. I work with AI solutions and love what y’all did with OpenAI and would love to build thoughtful interactions like that with my builds. Even smart home integrations that could trigger special lighting effects would be awesome 3

The HOOMstead3 months ago