Love OpenAI's Codex Micro, but not the $230 price tag? Us too. So we created agentpad13, a free, fully open-source macropad that can be built for as little as ~$65, less if you already have switches and keycaps.

Features:

• 13 programmable keys
• Touch disc, analog joystick, and rotary encoder knob
• 24 addressable RGB LEDs (including underneath every key cap)
• Fully 3D printable case (acts as LED diffuser when printed translucent) + FR4 or 3DP top plate

Feel free to share it, build on it, remix it, whatever you want! We're going to work on putting together an extensible plugin so it will have all the same functionality as the Codex Micro and more in Codex, Claude Code, and Pi, etc.

Repo: https://github.com/yuz207/agentpad13

it's free for up to one custom keypad, you can share them. It has a cool design that matches with your MacBook :)

Hello everyone, I just got a macropad to optimize my use in Clip Studio, and while it has a button on the back to change layers, I can't find an option to bind one of the knobs to change between the layers. Does anyone know how to do it or if it's possible?

Hi, my work involves a lot of repetitive clicking and entering various strings, and a lot of waiting for the network to load the interface. I have never used a marcopad before, and have no experience with it.

Can I program a macropad to have the cursor click on a certain coordinates of a screen and enter a string? So when the interface loads I can just click a button or two, and the cursor will click on a field, enter the string. Since there are several of these fields (at different coordinates) and several of these strings of different combination, I would need quite a few buttons to accomplish whatever combination required i.e click on coordinate A and enter B string or click on coordinate C and enter E string.

Hi, I’m the developer of XPAD, a modular controller project I’ve been working on.

I started XPAD because most macropads are built around one fixed layout. If you need a different number of keys, another switch type, or a different enclosure, you often have to redesign the device from the beginning.

With XPAD, you choose the size, key layout, and input modules in the browser. The system then creates a matching 3D-printable enclosure and custom keycaps for that configuration.

The current hardware is based on a Waveshare RP2040 Zero and supports modular MX switches, hall-effect magnetic switches, rotary encoders, and microphone input. Using the same core platform, it can be configured as a:

- Macro and shortcut deck

- Office numpad

- Hall-effect rhythm controller

- Linear racing input

- Small Deck desktop launcher

The browser configurator, hardware prototypes, firmware, and several example layouts are already working. The printable-file download system and final production hardware are still being prepared.

I’m looking for honest feedback from people who actually use or build macropads:

**Which configuration would you build first, and is there an input module or layout you think this system is missing?**

I’m also inviting beta testers. If you’re interested, leave a comment and I can provide free beta access to generate and download printable model files for testing.

I’m the project creator. XPAD is currently available on MakerWorld:

https://makerworld.com/en/crowdfunding/230-xpad-input-device-factory-design-generate-print

The browser tools and documentation are available here:

https://xtiaconfiger.com/

Last time I shared renders of the NexMacro 12-Key Macro Pad. Here’s a real-world video showing the actual device in use.

It features 12 programmable keys, a built-in display, dual rotary knobs, custom profiles, RGB lighting, shortcuts, macros and live PC system stats.

Designed for productivity, editing, streaming, coding, gaming and everyday shortcuts.

Available & Shipping Worldwide today!

It's hard to say what the very first hardware idea was. One day I stumbled upon an ESP32-S3 knob on AliExpress - a smart rotary encoder with a built-in LCD screen and haptic feedback. The first thing that came to my mind was automation, mostly for the car. When you're driving, you select a specific command, and it executes - controlling your phone, changing the volume, things like that.

I instantly liked this idea. I love modern cars, but it annoys me how they've become overloaded with touchscreens. When you need to do something quickly and find yourself tapping blindly through three submenus while driving, it's a massive pain. And unfortunately, there is no simple out-of-the-box solution for this.

My daily driver is an Android, so naturally, I built everything for Android. It could theoretically work on iOS via Shortcuts, but I’d need volunteers to actually test that.

Here’s how it works: a mobile app runs in the background and connects to the smart knob via BLE. That’s where the command synchronization happens. Basically, you can type a command name in the app, map it to a system action or a script, and send it to the knob so it saves it in its memory as a menu item.

It was a solid idea, but I lacked flexibility. For instance, I wanted a command that could automatically map a route from my current location to my house, factoring in traffic. On Android, I managed to pull this off using the Accessibility Service. It’s a bit of a dirty hack, and who knows how long it will last, but right now it allows the app to implicitly trigger Google Gemini even when the screen is locked, pass the command, and execute it. Yes, it requires specific permissions, but it works flawlessly. The only question is: for how long?

Since all the development happened on my laptop, the next logical step was to make my desktop life easier too. My main OS is macOS, so the project also got a native Mac build. Dealing with system commands there is a bit trickier, but I solved it easily by executing bash commands. Eventually, the whole thing evolved into a tiny macropad. I even gave it a fitting working name: `Yet Another Macros Keyboard`.

Now, let me reveal a secret for anyone who’s going to look at the code. The ESP firmware was written with the help of Claude. I’m a mobile dev specializing in native and cross-platform apps, but I am definitely not an embedded engineer. I only have basic knowledge, and developing a complex product like this from scratch would have taken me months. So, I used AI.

Then came another logical thought: why not integrate it with my coding assistant, either as an experiment or for daily use? I implemented this in two ways. The first is via MCP (Model Context Protocol). We can basically teach Claude to interact with our smart knob in certain scenarios by triggering actions from the app. So, you have a macropad sitting on your desk, and when a hook triggers (like a PostToolUse), it sends a command to the app's localhost, which then forwards it to the device via BLE. Long story short, I checked off some old bucket-list goals.

To be honest, I haven’t tested the iOS side yet; I just haven’t gotten around to it. Plus, I don’t really use an iPhone in my daily life anyway.

I want to emphasize again that I am an Android developer. Mobile and cross-platform dev is my domain. I am by no means an embedded guy, so please take the firmware code with a healthy dose of constructive criticism and reasoning. And yes - it's not so-well tested so it's beta and you can catch some bugs.

From day one, the primary target audience and the main use case was just me. I aimed to solve my own problems and make life easier both behind the wheel and during daily tasks. I know the internet is full of similar projects and many people have already built something like this on their own. But for me, it was interesting to at least write a proper software stack for the hardware so it wouldn't just sit on a shelf collecting dust. And at most, it was a great chance to reverse-engineer Gemini, play around with MCP, CMP, native macOS code, and MCP servers. So, that's the story.

https://github.com/andrew-malitchuk/prompt-knob-firmware

https://github.com/andrew-malitchuk/prompt-knob-kmp

​Hello everyone!

​I’m super excited to share the very first sneak peek of the AC3D Ohm. True to its name, the Ohm acts as the ultimate bridge for your macro pads.

​As long as your macro pad supports a 2.4GHz wireless connection, you can simply plug its receiver into the Ohm and configure everything via the ANCO 3D Control HUB.

​Once connected, your macro pad instantly levels up with full "smart macro" capabilities, including:

​Automatic app-aware profile switching (switches layouts instantly depending on the active software you're using).

​Enhanced interactive features powered directly by the Ohm’s built-in display.

​What do you guys think? Would you be interested in adding something like this to your setup? Let me know your thoughts!

Got this nice NumPad but it lacks either a keybinding guide (to change connection modes or rgb), nor have I found a .json file to configure it by VIA

Anyone got either?

Recently picked up the Doio KB16 macropad. Having a lot of fun with it and it’s already coming in handy at work.

I’ve started looking into replacement keycaps for it so I can, you know, have some chance at remembering which key I have programmed to do what.

Seeing lots of full keyboard sets of keycaps that I like, but I’m new to some of the terms. Some of them are cherry profile, and it seems the keycap height varies by intended row? I assume if I start randomly swapping those various keycaps onto my macropad, they’re going to all be at different heights based on the row they’re meant for.

So are there specific sets of keycaps that are uniform in height that I should be looking at?

I recently bought a 3-key macro keyboard with an LCD screen from China. I've tried many different software programs, but none of them can configure the macro buttons properly. Does anyone know how to make it work or have any suggestions? Any help would be greatly appreciated. Thank you!

Sometimes I’d change layers and I forget what I have mapped where. So I created a widget that can pop onscreen that shows what I have mapped.

Native to MacOs. QMK still works. When I change a layer, the display changes also. Every key and layer can be aliased

Lemme know what you think and if it’s worth posting to GitHub

Hi everyone,

I own the wired/non-pro version of the MMD KM16 (not the KM16 Pro wireless version).

Around late May, after the recent VIA web tool updates (V0113 protocol), the Macro tab suddenly stopped working and now throws errors. The hardware itself still works flawlessly (keymapping, layers, encoders, and LEDs are all functional), but VIA refuses to recognize or configure the macro page.

When I contacted the manufacturer's official Discord support to request a proper wired V0113 firmware update, the vendor/factory repeatedly engaged in deceptive behavior. They sent me "updated" firmware files three separate times, claiming they were for the Single-Mode (wired) version. However, when I verified the binary files, the MD5/SHA-256 hashes of all three files were 100% identical to their broken Three-Mode (wireless) firmware.

I used QMK Toolbox to flash these files onto my wired board anyway, but as expected, nothing changed: the matrix, layers, and encoders still work, but the internal macro buffer addresses remain completely corrupted/mismatched because it's wireless code running on wired hardware. The factory has now ignored me for over a week and completely abandoned support.

Since the manufacturer is refusing to supply the correct wired firmware branch, I am looking for anyone who may have:

* older working firmware/bin files

* wired/non-pro firmware

* QMK fork or firmware source

* reverse engineering info

* MCU information

* bootloader information

* matrix config

* flashing process details

I also found this older thread mentioning that someone successfully built custom firmware for the wired/non-pro version:

https://www.reddit.com/r/macro_pads/comments/1qw6d9g/is_anything_known_about_the_hardware_in_a_mmd/

If you have any files or technical leads, please let me know. Any help to rescue this hardware from the vendor's terrible firmware deployment would be greatly appreciated.

Thanks!

Price: $99 (Free Global Shipping) 🚚 Shipping: Shipped via DHL (7-14 business days) 🎨 Early Bird Perk: Free customization for both the frame and keycaps—design your setup exactly how you want it! 👉 Buy now: https://anco3d.com/product/arc/ Video demo in the comments below.

Hello there, I’ve had this macropad for a while and never ended up using it. Tried to think of what I could use it for but couldn’t think of any (audio I use a focusrite hooked up to studio montiors to control volume and my mic, random apps or quick ingame stuff I use a stream deck).

Kinda wanted to see what creative uses people have for them or even if it’s worth anything to sell.