/work/codex-micro
July 2026 · Work Louder · public collaboration with OpenAI · Firmware and product UX developer

Codex Micro · firmware and product UX

Through Work Louder, I contributed to the firmware and experience of Codex Micro, turning Codex workflows into clear and coherent physical interactions.

A physical controller for Codex

Codex Micro was created through the public collaboration between Work Louder and OpenAI. It brings useful Codex actions and information onto the desk through dedicated keys, lighting, a rotary control, and a joystick.

The product does not replace the application. It provides a physical point of access to recurring workflows and makes it easier to understand when an activity needs attention.

Codex Micro

Codex Micro, created by Work Louder in collaboration with OpenAI.

The official product page presents four main ways to interact with Codex: Agent Keys communicate task status through color, Command Keys keep frequent actions close, the dial adjusts reasoning level, and the joystick launches configurable skills.

Public Codex Micro experience: physical controls, Codex functions, and the outcome for the developer

The public product functions converge into a more physical and immediate workflow. The diagram describes the officially presented experience, not the internal architecture.

My contribution

As part of the Work Louder team, I contributed to the firmware and to the definition of the product experience.

My work focused on:

  • turning the product concept into understandable device behavior;
  • coordinating physical controls, visual feedback, and Codex-related functions;
  • keeping interactions coherent across everyday use and dedicated workflows;
  • developing and refining the firmware features required by the experience;
  • validating the device behavior with the wider team.

The main challenge was keeping a product that connects software, physical controls, and immediate feedback simple. Every element needed to communicate its purpose without turning the controller into another interface that constantly demands attention.

My contribution was not limited to connecting a command to a key. I worked on the meaning of the interaction: what the person needs to understand before acting, which response should follow, and when the device should remain quiet.

Giving state a physical form

An application can use text, windows, notifications, and history. An object on the desk has a much smaller set of signals. That limitation is also its value because it forces the product to choose what genuinely deserves attention.

For Codex Micro, I worked around a simple hierarchy:

  • status should be recognizable at a glance;
  • the available action should match the physical control;
  • feedback should arrive without interrupting the work;
  • the meaning of each signal should remain stable over time;
  • customization should not erase the identity of the product.

Firmware therefore becomes part of the communication. It does not only execute an input, but helps make the relationship between digital activity and physical control understandable.

An experience built around real work

I treated Codex Micro as one product rather than a collection of shortcuts. Keys, light, movement, and device response needed to use the same language and help the user move from intention to action with less friction.

That approach required firmware development and product UX to evolve together: understanding the workflow, deciding which feedback was genuinely useful, and refining the behavior on the physical device.

Configurability also requires care. A dedicated controller should adapt to different people and habits, but it still needs to be understandable as soon as it is connected. I therefore kept the defining product functions at the center and treated customization as a way to expand the experience rather than replace it.

Collaborating on a shared product

Codex Micro brings together different disciplines: OpenAI's software product, Work Louder's hardware and industrial design, the firmware, and the way all these layers become one experience.

My work required translating goals from those different disciplines into behavior that could be evaluated on the device. Design and development moved together: an interaction decision could require a firmware refinement, while a test on the physical product could show that the intended feedback was too complex or not visible enough.

That cycle allowed me to contribute not only to the technical implementation, but also to the clarity of the final product.

Outcome

My contribution supported a compact and recognizable controller designed around public Codex workflows and officially presented as part of the collaboration between OpenAI and Work Louder.

The project represents how I like to work: connecting firmware, interaction, and product identity to make an experience that spans hardware and software feel natural.

It also demonstrates an aspect of firmware that I consider essential: code becomes part of the product when every technical response corresponds to a clear meaning for the person using it.

What this project says about my work

Codex Micro brings together several skills that I contribute to embedded projects:

  • firmware development shaped around product behavior;
  • interaction design across software and physical controls;
  • visual feedback treated as part of the experience;
  • collaboration across different teams and disciplines;
  • validation and refinement on the physical device.