Skip to main content

[SOLVED] Codex Micro: ChatGPT overrides underglow on non-Codex layers

Bugs

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:

  1. In Input, configure Layer 2 with custom key backlighting and underglow at nonzero brightness.

  2. Completely quit ChatGPT.

  3. Switch to Layer 2. Both the key LEDs and underglow work correctly.

  4. Open ChatGPT.

  5. 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.

Product
Input, Creator Micro v2
Posted by Zandre Azogue ·
Status: Completed11 comments

Log in to comment and vote

Comments11

  • Josh Cannon

    •

    Jul 22

    I am having the same issue

  • Eric Li

    •

    Jul 22

    +1, having the same issue with underglow definitely not working, and backlight behavior inconsistent.

  • Kiryl Chetyrbak

    •

    Jul 24

    yeah similar issues. everything that is non codex i do not have any glow effect at all

  • Koy Carraway

    •

    Jul 24

    Same issue for me. Underglow not working at all

  • Zandre Azogue

    •

    Jul 24

    Follow-up (I had Codex investigate): ChatGPT’s Codex Micro service sends its lighting commands without checking the device’s active layer. The Work Louder device API exposes the active layer as selectedLayerIndex, but ChatGPT does not consult it before sending v.oai.rgbcfg and v.oai.thstatus.


    After reconnecting, my Codex Micro reported firmware v0.4.1 and a non-Codex layer as active, but ChatGPT still sent—and the device accepted—its RGB commands. Input’s saved colors are therefore not being lost; they are being overwritten at runtime by ChatGPT.

    The fix should be to send Codex lighting commands only when the Codex layer is active. On Layers 2–6, ChatGPT should send nothing and leave Input’s lighting untouched. I reproduced this with Input 0.17.2 and ChatGPT 26.721.31836, build 5828.

  • Aviv Hadar

    •

    Jul 31

    Same issue here. VERY well versed in the design of these and incredibly talented at getting into the code/firmware/bootloaders. It’s a real bug. Needs to be fixed.

  • Zandre Azogue

    •

    Jul 24

    Yeah my initial report was just for the underglow but it affects both underglow and backlight behavior. Hopefully this gets fixed soon. Also noticed that if I’m on a different layer and a codex agent start running, it overrides the layer 2 lighting setting.

  • Daniel Becker

    •

    Jul 31

    Same issue with the beta updated Creator Micro 2 running the Codex Micro layer.

  • Levi Carver

    •

    Aug 1

    i am on 0.17.2 and still experiencing the same issue.

  • Aviv Hadar

    •

    Aug 2

    This is fixed with the most recent firmware update to 0.6.1.