Backlog
151Under consideration
Anthropic Claude - Creator Micro 2
Add Claude integration for the Creator Micro 2.
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.
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.
Using Wispr Flow with Creator Micro 2
I use Wispr Flow heavily, and I was hoping to map the shortcut that triggers dictation to Wispr Flow to a key on my Creator Micro 2, but it doesn't seem like that works. I don't understand why. Does anyone else have this issue?
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.
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.
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?
Is Creator Micro 2 also detected by Codex / ChatGPT app?
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)
Add a macOS / Apple Keyboard preset for native Mac function keys
Iโd like to request a dedicated macOS / Apple Keyboard preset in Input. Instead of only adding a few individual shortcuts, it would be very helpful if Knob1 could support a more complete set of macOS-native system keys and function-row actions, so it can behave more consistently with a native Mac keyboard. For example: Globe / Fn Spotlight Search Do Not Disturb โฆ Some of these actions can be recreated with custom shortcuts or third-party tools, but having them built directly into Input as official macOS actions would make the experience much easier, cleaner, and more reliable for Mac users.
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.
Next up
15Committed and queued
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
Switch to a "default layer" when no linked software is in focus
I love my Creator Micro, but there is one feature I wish it had. I really like how it switches layers when a specific program is in focus, but it would be great if it reverted to a default layer when no specific programs are active. When Iโm working in Illustrator, I don't want the same functions active in Chrome or File Explorer. Itโs possible this feature already exists and I just havenโt found it yet.
Input support for the Creator Micro v1 (legacy)
A firmware update to use the CM1 with Input app! ๐
Input UI improvements
Idea: Improve โActionsโ and โMultiโ tabs to allow individual key assignments to be done via the icon grid, rather than selecting from the nested drop down list. The drop down list is โhardโ to navigate: Key names are often truncated (shared sentiment with existing feedback posts) Drop down list shows 5 selectable keys in view while 10 section labels are always visible โ> only 1/3 of the 'rowsโ are actionable Feels sluggish for the core feature IMO, it would be much easier to select keys from the icon view thatโs already used when assigning keys from the โBasicโ list to Framer. Screenshot below shows how much unused space is available and how this could fit cleanly (says the non-UI guy making mocks in Excel). 2 less clicks per key assignment, โ less scrolling (NOW thatโs what I call IMPACC) More direct, less navigation Visible keys per view go from 5 โ> 40+ Consistent UI for all 3 tabs Appeases that 1 annoying customer who made 3 posts in one day
More options for the CM2 joystick please (also in desperate need of more documentation)
I received my Framer CM2 a few days ago, and I had been hoping to use the joystick on the CM2 for arrow keys so I wouldnโt have to take up four whole buttons for them, but apparently there is no way to remap the down direction on the joystick. It would be nice if there would be a way to move or get rid of what Iโm told is the radial backout option (as an aside: if the device is meant to be displaying some kind of menu when using the joystick, I have not been able to get that to display nor is there any documentation describing this feature or how it works). I saw in the backlog in the discord one of the WL people claimed there would be a way to toggle the joystick between the menu and โjoystick modeโ but that does not appear to be the case as far as I can tell (unless Iโm missing something, again there is no documentation to reference). Personally, Iโd appreciate it if there was an option to use the joystick just for regular keystroke inputs without a menu (ideally on press rather than on release in this sort of mode). And also itโd be nice if there was some kind of documentation at all about the features of both the CM2 and InputโIโve seen the setup video/quickstart guide, but while it looks very nice, I donโt mean to be rude, but itโs wholly inadequate even to introduce the productsโ basic features. As I alluded to before, I wouldnโt even know there (maybe? is this even still a thing?) is supposed to be some kind of menu appearing when using the joystick, or what that un-remappable X is meant to represent if I hadnโt been lurking the discord for months for updates on the project.
Automatic Power-Off
Not sure if this is a function but if so it doesnโt seem to be working on mine. But I accidentlly left my Creator Micro V2 on overnight and it didnโt automatically power off. Is this a feature, if not, is it something the user could set to do, along with how long till it does this within Input?
Feedback First hour of use.
Just getting to know the keyboard, but some things I'd really like to see after first impressions (Iโm on Mac M1 btw). Auto-detect default: Iโve set up a layer to auto-detect on a particular bit of software, but when I exit that software, I'd like the device to reset the layer back to layer 1. I can't see anywhere where this is possible. I have to manually touch the layer select button to go back to layer one. It would be great to be able to select a layer that auto-selects when no auto-detect software has been detected. Edit radial button broken? The edit radio button menu is broken in the latest release. In the setup video, you show the ability to add multiple options when using the radio button, but I can't see that menu anywhere. Rotate button cycle through different actions: I think I can achieve the same feature with the radial button (if the edit button gets fixed) but I'd love to be able to cycle through a set of actions by rotating the dial. For instance, I'm using Claude code, and I'd like to cycle through a defined set of shortcuts as I rotate, rather than it essentially acting as a repeater for the same key Open Software: I'd love to be able to open specific software with a key press! Repeated options in modifiers: when I create an action and assign a key, looking into modifiers: Option, Command, Control, and Shift are repeated in the menu. They are also repeated under modifiers under basic
Backlight and Underglow Brightness Control via Key Press
Like with the Knob1, it would be very useful to have these as things you can bind for on the go, when you canโt open Input for any reason (e.g., being in a work environment that disallows external software that isnโt whitelisted).
Creator Micro v2 - Power saving features
Might already be on the roadmap, but a setting to determine the number of minutes before most of the LEDs DIM to save battery life. Maybe the bottom right key with the transparent cap stays on but dim to show the device is still on, but all the rest turn off to save batt?
Recording actions does not respect non-ANSI keyboard settings
I'm on a Mac and I use a QWERTY keyboard (Apple Wireless Keyboard) and it's set up in the settings to be Dvorak. When I go to record an action, it ignores this override and registers the key input of the QWERTY keyboard. I can imagine a world where some people would want to have this setting optional. So maybe some sort of indication or toggle to use QWERTY settings or keyboard override settings.
In Progress
12Actively being built
Creator Micro v2 Wont Sleep
The device doesnโt seem to want to sleep and subsequently keeps waking up my computer. Iโm on Mac M1 and have latest firmware installed
Battery Status
Would be awesome to have a way of knowing the battery status directly through Input app and/or through the RGB present in the Framer Creator Micro. Aside from when itโs in bluetooth mode, that forces me to remove the cable & connect wirelessly, I canโt see how much battery the device currently has.
Feedback on Inputโs UI and UX
As a product designer, I see several issues in Inputโs current UI and UX that impact usability, consistency, and perceived product maturity. Below is a structured summary of areas that could be improved: Once an icon is assigned to an action, there is no way to remove it without deleting and recreating the entire action. It would be more user-friendly to allow clearing or resetting the icon directly. When creating a new multi-action, selecting keys/actions from long dropdown lists can become cumbersome. Providing search within these dropdowns would make it much easier and faster to find the desired key or action. The interface appears to use multiple icon libraries, which results in visual inconsistency. Standardizing on a single, cohesive icon set (such as an open-source library like Lucide which contains thousands of icons) would improve visual harmony and make it easier for users to find relevant icons. Whenever an action is created or modified, the hardware updates immediately, which feels slow and interrupts the workflow. Providing a setting to switch between manual and automatic updates would make the experience more efficient. The โMy actionsโ section in the drawer can become difficult to manage when working with multiple apps and many shortcuts. As the list grows, it becomes harder to locate the right action. Allowing users to organize actions into groups or folders (for example, by app or context) would significantly improve navigation and usability. Requiring users to open a drawer every time they want to add or edit an action introduces unnecessary friction. Making this interface persistent (such as a sidebar that remains visible) would reduce repetitive interactions and make better use of screen real estate. Basic keyboard shortcuts are not consistently supported within Input. For instance, using โ cmd + A to select the entire HEX code in the RGB context menu does nothing. Supporting standard platform shortcuts (select all, copy, paste, undo, etc.) would make the product feel more polished and efficient for power users. From an accessibility standpoint, the app appears to use relatively small font sizes and button styles with insufficient contrast. Increasing type sizes where appropriate and ensuring buttons meet recommended contrast ratios would improve readability and make the app more inclusive. Many interactive elements do not have tooltips or any form of inline explanation. Adding concise, informative tooltips for icons, controls, and less obvious features would reduce the learning curve and help users build confidence faster. Overall, the app currently gives the impression of being somewhat unfinished or in an early stage. Addressing the issues above, tightening visual consistency, and refining interaction details would substantially improve the quality and maturity of the product.
Create Groups for Actions/Multi Actions
It would be helpful if we were able to create custom groups of actions and multiactions to be able to organize them. At this point i have to hover to figure out if an action is set for mac or windows or app specific. If we could group them(like when you import presets) it would be much easier.
Knob1, Nomad - GIF Support
WL Team Edit: GIF Support is planned for Q2 2026. Upload a static image to Input and AI will create an animated/looping gif of your image for the display. Users can also directly upload an existing gif as a background for the Nomad and/or Knob1.
Firmware update issue Input NomadE
With the NomadE keyboard connected (software v0.3.3), my Mac Pro updated to the latest OS keeps showing this error message again. It has been happening for quite a while and across several updates. Any advice?
Creator Micro V2 USB only, ignore Bluetooth
I have multiple computers that I switch between. I want to have my Creator Micro V2 wired into my monitor/hub and it would just work with any computer I hook to that monitor/hub. But every time I disconnect a computer it goes into Bluetooth mode (first LED flashing fast and blue pulsing underflow), and it doesnโt exit that mode when you plug in the new computer. You have to tap on the touch button 3 times to cycle through all the Bluetooth paring slots, and get back to USB. Is there some way to have it always prefer USB, or disable Bluetooth entirely? Currently on firmware v0.4.0, Input 0.17.1
No device found error Creator Micro v2
Hi, I was setting up the new device for a bit and tested around in Figma, and the โinputโ app somehow suddenly not recognizing the device anymore and showing the โNo device found Please connect your deviceโ message. Firmware has been updated to v.023 when first connected. Also tried connecting the device via BT but it didnโt show up in the Near By Device section. Please help debug this. Thanks. Btw if user can reset the device to default with the device itself it would be great.
Creator Micro v2 - Battery Drain Over Bluetooth
Iโve noticed a severe battery drain issue when using my Figma Creator Micro Pro in Bluetooth mode. When the device is fully charged and I switch to Bluetooth, the battery drops from 100% to 1% within a few minutes. I can literally watch the percentage decrease in real time in macOS System Settings. This makes the device essentially unusable in wireless mode. I understand that battery life wonโt be unlimited, but I would expect at least a couple of hours on a full charge, not just minutes. To rule out lighting as the cause, I tested two scenarios: Backlight intensity at 50% (my usual setting when plugged in) Backlight intensity at 0% In both cases, the battery drained extremely fast with no noticeable difference. I can also see that, when I press the on/off button the rgb lights going from green to yellow shortly after connecting FCM throug bluetooth (and the device was plugged in the entire day to my Mac mini). Input version: 0.12.5 Firmware version: 0.2.2 OS: MacOS Sequoia 15.7.2
5 Reboots in 2 Days - Requesting a replacement (Defective Unit)
I received my Framer Micro v2 two days ago. At first glance, the build quality was amazing, and I really loved the design. However, my excitement didn't last long. After just 30 minutes of happily mapping keys, the device suddenly became completely unresponsive. I spent about two hours wrestling with it, and eventually had to open up the case to force a hard reboot on the PCB. After struggling for another hour, I finally managed to bring it back to life. (Yay!) But the relief was short-lived. Less than an hour later, it froze again. I rebooted it, it worked for an hour, and then it died again... It has been an endless loop. I've had to hard reboot this device five times in just two days. I think we can agree this is definitely not normal behavior. Just in case it was a connectivity issue, I even purchased two of the highest-quality cables available here in Korea to test it, but the results were exactly the same. This experience has been incredibly stressful. I would like to request an exchange for a fully functional unit or a refund.
Done
30Recently shipped
[SOLVED] Firmware Update v0.2.2 Kills the Creator Micro v2
SOLUTION: Follow the steps in this document Iโve just updated the firmware on the Creator Micro v2 (CMv2) to the latest firmware version (v0.2.2 I believe) and even though the software said that the update was successful, after unplugging it, the device wonโt turn on anymore at all. I went through a few TS steps, such as making sure Iโve got a functioning cable to test with plugging it in and then unplugging it. Made sure itโs fully charged, which it seems to be. SO far, nothing. Itโs dead. Bit at a loss nowโฆguess itโs a paperweight now? :(
[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.
Creator Micro v2, knob1 - Battery charging issue (MEGATHREAD)
Hey everyone, If youโre experiencing problems with battery charging on your Creator Micro v2 or Knob1, please read the whole post before installing the diagnostic firmware. IMPORTANT NOTE: This update does NOT include a fix. It is designed solely to gather diagnostic data so we can understand what is preventing the charging cycle from completing. Installing it is not mandatory, but your participation would greatly help us resolve the issue. Weโve already solved about 90% of the charging issues reported so far, thanks to everyone who submitted feedback. However, thereโs still a small number of cases where the problem persists, and we need to gather more information to identify and fix them. We are in contact with the chip manufacturer to figure out whatโs going on, and your detailed reports are essential. Please include in your comment: What exactly happens when you try to charge (LED behavior, percentage stuck, etc.) Which cable and adapter youโre using Whether charging ever worked correctly Any other symptoms To ensure we collect detailed diagnostic data on your specific case, we have created a custom version of Input and a matching device firmware with an integrated system which collects battery information and charging status. We kindly ask you to leave Input open in the background so the diagnostics can run continuously. You can keep using your device as usual during this process! The more data we are able to collect, the faster we are be able to provide a definitive fix. Instructions First, download and install the custom Input application that matches your operating system: Input for Mac (Apple Silicon): input-0.13.1-rc.4-arm64.dmg Input for Mac (Intel): input-0.13.1-rc.4.dmg Input for Windows: input-Setup-0.13.1-rc.4.exe Next download only the firmware that matches your device model from this post: Creator Micro V2 custom firmware: firmware_cmv2_v0.3.0-rc.2_merged.bin Knob1 custom firmware: firmware_knob1_v0.3.2-rc.3_merged.bin โ ๏ธ IMPORTANT NOTE: Due to the diagnostic data being sent from the device, you might notice a small delay in typing every 10 seconds. This is completely normal and will go away when you decide to go back to the stock firmware. Finally install the custom firmware, to do so follow these steps carefully: Open the Input application and connect your device via USB. (If you have other Work Louder products turn them off) Once the device appea
Creator Micro v2 - Cheat Sheet Overlay
WL Team Edit: We are planning to implement an overlay cheat-sheet (similar to what happens to the radial menu), you can trigger with a specific key. It would be incredible to do a higher end version of the Creator Micro where the keys have digital, backlit icons that dynamically change based on the layer youโre on, app youโre in, etc. I would pay extra money for that. To be honest, sometimes I forget what I mapped where on my blank keycaps (I keep them blank because I work within 3 main apps). I would be willing to pay a good amount more for this feature.
Creator Micro v2 - Open Apps/links/custom scripts
Iโve got a creator micro 2. Iโd like to be able to write custom scripts/macros. For instance, terminal commands or open certain apps or links (relying on default apps to open the links). In general, I could accomplish this with the ability to run shell scripts. For macos, I could accomplish this with the ability to run osascript scripts. (Thereโs also the Shortcuts appโฆbut that adds a lot of bulk/overhead and organizing them is a pita.) There are also third-party tools that allow the writing of custom macros, like [karabiner-elements](https://karabiner-elements.pqrs.org) and [skhd](https://github.com/asmvik/skhd) โ skhd is my personal preference because itโs super fast. Are there any workarounds or plans to do support this?
MacOS "We need Input monitoring permissions"
I keep getting the โWe need Input monitoring permissionsโ even though Iโve already provided the correct permissions. Iโve tried with both bluetooth and wired. Iโm using the Knob1 macOS Version 15.6.1 (24G90) Input Version 0.12.2 (0.12.2) It works fine on Windows.
Hello ๐๐ป
Hi everyone, this is a demo post! :)
Bug Report/Feature Request Form in Input
It would be great to add a bug report modal form to the Input platform. When a user submits a bug report or feature request, it creates an issue or ticket in the Input repository with the information provided by the user. To combat spam, authentication, such as GitHub authentication, would be necessary before allowing users to submit their reports or requests.
Action Icons Not Working
After watching the video on how Input works, I saw that I could add icons to actions on my FCM but currently itโs bugged & only shows momentarily before collapsing/hiding again. Input version: 0.12.2
Input updated now can't connect with cable for Nomad or Creator Micro
Just got the new creator in over the holiday break. I went to start working this morning, and Input prompted me for an update, so I went ahead and installed the update. Now neither of my WorkLouder products are connecting via cable to Input. Itโs frustrating because I am trying to program them.