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-w27105 about 1 month ago
Feature Request
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-w27105 about 1 month ago
Feature Request
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-w27105 about 1 month ago
Feature Request
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-w27105 about 1 month ago
Feature Request
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-w27105 about 1 month ago
Feature Request
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-w27105 about 1 month ago
Feature Request
Planned
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 Ribeiro about 2 months ago
Feature Request
Planned
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 Ribeiro about 2 months ago
Feature Request
nomad [e] fw v0.6.1 not detected by input 0.18.3, and flashing 0.9.0 from older input fails
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.
kate m 22 days ago
Bugs
nomad [e] fw v0.6.1 not detected by input 0.18.3, and flashing 0.9.0 from older input fails
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.
kate m 22 days ago
Bugs
Waiting for user
Creator Micro V2 repeatedly fails to reconnect over Bluetooth after sleep
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 about 2 months ago
Bugs
Waiting for user
Creator Micro V2 repeatedly fails to reconnect over Bluetooth after sleep
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 about 2 months ago
Bugs
Lighting problem (Figma Creator Micro)
I wanted to reset my key configuration, so I followed a guide and updated the firmware on my Figma Creator Micro using QMK*. However, after the update, the backlight settings disappeared. How can I restore the backlight configuration? https://i.imgur.com/HrmbGRL.png
onfreak 13 minutes ago
Bugs
Lighting problem (Figma Creator Micro)
I wanted to reset my key configuration, so I followed a guide and updated the firmware on my Figma Creator Micro using QMK*. However, after the update, the backlight settings disappeared. How can I restore the backlight configuration? https://i.imgur.com/HrmbGRL.png
onfreak 13 minutes ago
Bugs
Nomad [e] 2 media not working with an iPhone
I connected my nomad [e] 2 to my iPhone via bluetooth, I have musiv playing via Apple Music but it’s not showing up on the display. I am on iOS 27.2 with firmware 0.3.0-rc.16
Maxence Raynal about 1 hour ago
Bugs
Nomad [e] 2 media not working with an iPhone
I connected my nomad [e] 2 to my iPhone via bluetooth, I have musiv playing via Apple Music but it’s not showing up on the display. I am on iOS 27.2 with firmware 0.3.0-rc.16
Maxence Raynal about 1 hour ago
Bugs
Completed
[SOLVED] Codex Micro: ChatGPT overrides underglow on non-Codex layers
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 2 months ago
Bugs
Completed
[SOLVED] Codex Micro: ChatGPT overrides underglow on non-Codex layers
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 2 months ago
Bugs
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.
Matt about 2 months ago
Feature Request
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.
Matt about 2 months ago
Feature Request
MX Alpha on Lofree issue with space bar
currently having an issue with the space bar. I believe it’s an issue with the stabilizers being too tightly squeezed by the auxiliary pins around them. Has anyone ever had this issue? I’m thinking of either cutting it off or sand the space bar stabilizer keycap connector. Any ideas?
Primata 7 days ago
Bugs
MX Alpha on Lofree issue with space bar
currently having an issue with the space bar. I believe it’s an issue with the stabilizers being too tightly squeezed by the auxiliary pins around them. Has anyone ever had this issue? I’m thinking of either cutting it off or sand the space bar stabilizer keycap connector. Any ideas?
Primata 7 days ago
Bugs
Make usb-connected codex micro sleep on PC sleep
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 about 1 month ago
Bugs
Make usb-connected codex micro sleep on PC sleep
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 about 1 month ago
Bugs
Endless Bootloader Mode
I recevied my creeator micro 2 after coming back from a trip, and after connecting it to my windows pc via usb, the input software prompted me to update to the lastest firmware, however, after it showed that it was successfully installed, the device seemed to be kept in the bootloader mode with that yellow glow. I tried soft reset and re-try the process but no luck. If you have any clue on how to fix the issue, please do let me know! Thanks!
Yanlin Du 10 days ago
Bugs
Endless Bootloader Mode
I recevied my creeator micro 2 after coming back from a trip, and after connecting it to my windows pc via usb, the input software prompted me to update to the lastest firmware, however, after it showed that it was successfully installed, the device seemed to be kept in the bootloader mode with that yellow glow. I tried soft reset and re-try the process but no luck. If you have any clue on how to fix the issue, please do let me know! Thanks!
Yanlin Du 10 days ago
Bugs
Getting current layer id in Python
Hi, I am creating a software synthesizer from scratch and I am using my Creator Micro2 as an input interface. I was wondering if I could detect changes in the 3 hardware layers (when I change the layer using the touch interface) through HID in Python? I do not want to assign physical keys for layers. Is the touch interface layer change not exposed in the HID data packets? It would be great to detect programmatically when I change the layer in hardware.
Arun S 11 days ago
Feature Request
Getting current layer id in Python
Hi, I am creating a software synthesizer from scratch and I am using my Creator Micro2 as an input interface. I was wondering if I could detect changes in the 3 hardware layers (when I change the layer using the touch interface) through HID in Python? I do not want to assign physical keys for layers. Is the touch interface layer change not exposed in the HID data packets? It would be great to detect programmatically when I change the layer in hardware.
Arun S 11 days ago
Feature Request
Creator Micro V2: all keys double-fire (chatter) — persists after factory reset AND firmware 0.6.1
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 about 2 months ago
Bugs
Creator Micro V2: all keys double-fire (chatter) — persists after factory reset AND firmware 0.6.1
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 about 2 months ago
Bugs
Adding input to Homebrew
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 about 2 months ago
Feature Request
Adding input to Homebrew
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 about 2 months ago
Feature Request
Next/previous recently viewed chat actions do nothing in Codex
The actions trigger but have no effect whatsoever in Codex. I would have expected these to acts as forwards and backwards arrow do in a web browser.
Thomas Tiotto 13 days ago
Bugs
Next/previous recently viewed chat actions do nothing in Codex
The actions trigger but have no effect whatsoever in Codex. I would have expected these to acts as forwards and backwards arrow do in a web browser.
Thomas Tiotto 13 days ago
Bugs
Many issues
I’m having real trouble using my new Creator Micro 2 with Codex, which is what I bought it for. I connected it yesterday on BT#1 and this morning it wouldn’t connect and I end up having to pair it again, still on #1, which leads to both showing up, somehow. My presets keep disappearing from my keymap as I keep having to reconnect the Micro and I guess Input thinks it’s a new device. Codex shows it as connected but it is not working because the ChatGPT preset randomly disappears from the available ones.
Thomas Tiotto 13 days ago
Bugs
Many issues
I’m having real trouble using my new Creator Micro 2 with Codex, which is what I bought it for. I connected it yesterday on BT#1 and this morning it wouldn’t connect and I end up having to pair it again, still on #1, which leads to both showing up, somehow. My presets keep disappearing from my keymap as I keep having to reconnect the Micro and I guess Input thinks it’s a new device. Codex shows it as connected but it is not working because the ChatGPT preset randomly disappears from the available ones.
Thomas Tiotto 13 days ago
Bugs