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.
Can’t tell, but seems like my device came with old or broken firmware, or there’s a bug with the Input app. Input 1.0.0 can't read my Creator Micro 2's firmware version. device.status returns 404, and the legacy 'version' request times out, but sys.version returns v0.1.50. So Input never offers the firmware update. None of my LED lights change for anything, they appear stuck on white no matter the setting. Codex reports “Creator Micro input remains available, but lighting and battery updates are temporarily unavailable” and “Connected with limited functionality”
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.
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.
SUMMARY While Input is running with its normal Dock icon visible, a second matching Input icon repeatedly appears beside it and immediately disappears. The Dock expands and contracts around the transient entry. The main window remains open and usable. The window movement in my recording is intentional: I am dragging it to demonstrate that the window works. The defect is the duplicate, flickering Dock icon, not the window movement. ENVIRONMENT • Input 1.0.0 (bundle identifier: it.focusense.input-app) • macOS 27.2, build 26B5091g; arm64 • Bundled Electron 40.10.6 • Creator Micro 2; firmware 0.6.3-rc.12 reported in Input's log • Observed 29 September 2026 OBSERVED BEHAVIOR 1. Input is already running, with the main window open and its usual icon in the Dock. 2. A second matching icon briefly appears next to it. 3. The extra icon immediately disappears and returns intermittently. The behavior repeats within a 13.35-second recording. The extra icon is visible near the start, absent around 2 seconds, and returns around 3.5 seconds. Dragging the window is not an established trigger. A clean-start reproduction recipe and frequency across separate sessions are not yet established. EXPECTED One stable app representation while Input is running, without an unexplained second icon repeatedly entering and leaving the Dock. IMPACT Distracting Dock flicker and layout movement. It looks as though Input is repeatedly launching even though its main window remains usable. No crash or data loss observed. INVESTIGATION — CAUSE NOT YET CONFIRMED A later process check sampled 20 times over roughly five seconds and found one stable main Input process plus the same four Electron helpers. All installed helper bundles declare LSUIElement=true, and Input requests a single-instance lock. No second main process was observed. This sampling was not synchronized with the original recording and cannot exclude very short-lived child processes. Read-only inspection of the installed app shows explicit app.dock.show()/hide() calls around main-window creation/destruction, tray reopen, and autostart. Electron 40.10.6 contains a workaround for rapid Dock hide/show transitions causing duplicate icons on macOS. This is an investigation lead, not proof that those transitions caused my symptom: https://github.com/electron/electron/blob/v40.10.6/shell/browser/browser_mac.mm#L474-L530 The radial-menu and cheat-sheet windows are transparent, non-focusable macOS panels configured with skipTaskbar:false. Their lifecycle is another path to check; that setting has not been established as the cause. RELATED REPORT / MORE SPECIFIC LEAD I found this existing report describing similar Dock behavior on the same macOS build: https://feedback.worklouder.cc/p/inputs-dock-icon-repeatedly-bounces-while-the-application-remains-running That reporter observed short-lived osascript processes launched by AppSense registering under Input's bundle identity as foreground applications. Their follow-up says a local change to read NSWorkspace.sharedWorkspace.frontmostApplication stopped those foreground registrations while polling continued. These are the other reporter's findings, not independently verified on my installation. Please consider whether my duplicate-icon symptom is the same issue and link or merge it if appropriate. REQUESTED CHECKS • Identify the transient Dock item's owni
macos, apple silicon. nomad [e] on firmware v0.6.1. input 0.18.3 never detects the keyboard – “no device found” – even though macos enumerates it correctly: • usb product name = “nomad e”, idvendor 0x303a, idproduct 0x1001 • serial port /dev/cu.usbmodemf09e9e10355c2 present • not in esp32 rom bootloader • display and menu fully responsive what worked: rolling input back to 0.6.1-rc.1. it detects the keyboard immediately. so 0.18.3 appears to have lost support for firmware v0.6.1. second problem: from input 0.6.1-rc.1, setup > download latest firmware version 0.9.0 downloads the file but flashing fails with “there has been an error! retry”. retried several times, same result. device still on v0.6.1 and still working, so nothing was bricked.
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.
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.
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.
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.