AM Configurator 0.1.66

AM Configurator 0.1.66

AM Configurator 0.1.66 is a normal public release of the independent, open-source desktop editor for Angry Miao keyboard profiles. It is a community project and is not affiliated with or endorsed by Angry Miao.

Highlights

• Edit key assignments on keyboard-shaped layouts, with every available layer kept in reach and firmware-level labels available only when wanted.
• Build macros three ways: type the text in Text entry with Fast (10 ms), Slow (100 ms), or Natural timing (a WPM target or your own captured typing cadence); edit every event's key, down/up, and pause in Flow, with combos such as Ctrl+Alt+Del as ordinary rows; and append a Repeat of any key press with its capacity cost quoted before anything changes. Recorded macros stay editable in all modes.
• Paint lighting frame by frame, import GIF, PNG, BMP, or JPEG media, and build local Pulse, Hue cycle, Sweep, Shimmer, and Move & zoom effects.
• Preview lighting before applying it, and save reusable keymaps, macros, lighting, media, and compatible profiles to the Library as separate explicit actions.
• Use manual Keymap, Macros, Lighting, Library, profile, and device workflows without enabling AI or creating an AI account.
• Work with model-specific layouts for CyberBoard, AM Relic 80, AM AFA/AFA 2, and AM Neon 80. CyberBoard switch LEDs follow its physical key geometry while its 40×5 top display remains a separate rectangular canvas.

Downloads

The release contains exactly these five files:

• AM-Configurator-0.1.66-macOS-arm64.dmg
• AM-Configurator-0.1.66-Windows-x64-Setup.exe
• AM-Configurator-0.1.66-Linux-x86_64.AppImage
• SHA256SUMS.txt
• release-manifest.json

Download them only from the AM Configurator 0.1.66 GitHub Release.
The macOS bundle is ad-hoc signed but is not notarized, and the Windows installer has no Authenticode publisher signature. Verify the hash and GitHub build attestation before using the narrow per-application first-launch steps in the installation guide; do not disable operating-system security globally.

Supported keyboards

• CyberBoard: up to seven keymap layers and 32 macros, switch LEDs, and the 40×5 top display.
• AM Relic 80: up to seven keymap layers and 32 macros, per-key lights, and seven edge lights.
• AM AFA / AFA 2: up to seven keymap layers and 32 macros, Alice-layout key lights, and centre body lights.
• AM Neon 80: four keymap layers, 16 macros, 89 axial LEDs, a 46×5 head matrix, and the side-screen lights derived from that matrix.

Firmware revisions differ. Keep a complete portable JSON profile and any original lighting media before writing to a board or firmware version you have not used before.

Connect, read, edit, and write

1. Connect one keyboard over USB, close other configurators that may hold its HID interface, and read its keymap and macros. Reading never writes.
2. Edit Keymap, Macros, or Lighting. Preview imported or animated lighting before applying it to a slot.
3. Save a portable JSON file. Saving reusable work to the Library remains a separate labelled action.
4. Start a full write only when ready, verify the displayed device identity, type the requested confirmation, and keep the cable connected through verification. AM Neon 80 also requires its physical Esc+F2 unlock.

A full write replaces keymaps, macros, and LED data together. Keymaps and macros are read back where the protocol supports it. Neon firmware does not expose LED read-back, so reading a Neon is not a backup of its current lighting; retain the original lighting source and verify lighting visually after a write.

Optional AI

AI is optional and off by default. All manual tools remain available while it is off, and the application does not automatically contact or discover an Ollama server. If enabled, a configured Ollama server or Direct API provider can generate validated procedural LED settings that are rendered locally by AM Configurator. Each explicit Generate action makes one request and never retries automatically.

Remote provider paths are experimental and are not presented as release headline features. They may use paid provider accounts, and they are not claimed as live-qualified unless the exact release evidence says so. Keymaps, macros, imported media, device identifiers, and Library files are not sent as part of a generation request.

Qualification boundary

• Automated checks cover the supported platforms, package contents, device protocols, model geometry, profile compatibility, and the manual application paths. Native installers are built and smoke-tested on macOS arm64, Windows x64, and Linux x86-64.
• The exact Windows package was installed, audited, smoke-tested, and uninstalled successfully. Trust-warning behaviour and a separate Windows About launch remain established baseline evidence and were not reenacted.
• The Neon device path has prior physical validation and sustained use on one AM Neon 80. The owner accepted that evidence for this release; no final-candidate hardware write was performed. Other keyboard families have implementation, fixture, protocol, geometry, and regression coverage rather than a claim of physical testing for this release.
• AI providers are outside the release headline and are not claimed as live-qualified on the exact candidate.
• Experimental Windows ARM64 and Linux ARM64 builds exist as best-effort CI artifacts only. They are not part of this release, are not qualified, and are not supported platforms.

Integrity and provenance

Compare the installer with SHA256SUMS.txt, then verify the free GitHub build attestation:

gh attestation verify <downloaded-file> --repo roethlar/AMKB-GUI

Hashes prove byte identity, and attestations bind those bytes to this repository and its build workflow. Neither substitutes for a platform-trusted publisher identity.

Reporting a problem

Use the structured bug report and include the keyboard, operating system, AM Configurator version, operation, and exact installer filename. Remove API keys, device serials, personal paths, and private macro or profile contents before posting.