You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support the Work Louder Codex Micro in the desktop app
#28674
The Work Louder Codex Micro is a desk controller built for agent work: six
agent keys with status LEDs, seven command keys, a knob, and an analog stick. Codex's desktop app
drives it: each agent key follows a thread and lights up with its state (working, needs input,
unread, error), and the other controls approve, decline, stop, and so on.
In T3 Code the device does nothing. People who use T3 Code instead of Codex, or alongside it, have no
way to see agent state on the device or answer approvals from it.
Prior work
@Hormold implemented this in #23869. It was closed only because it lacked prior approval; there were
no technical objections. I've rebased that work onto v0.1.6 and I'm running it on macOS with a real
device. This discussion asks for approval of the direction and scope before a PR.
Proposed scope
Desktop only. The device is a local USB/Bluetooth HID peripheral, so web and mobile can't reach it.
The desktop app owns the connection and drives whichever environments it's connected to.
Device link in the Electron main process (apps/desktop/src/codexMicro), using node-hid
against the device's vendor interface (VID 0x303a, PID 0x8360, usage page 0xFF00). It speaks
the device's own newline-delimited JSON-RPC protocol: status, lighting config, per-key lighting,
key, knob, and stick events. It does not use Work Louder's SDK.
IPC bridge: an optional desktopBridge.codexMicro with getState, setLighting, and onEvent,
typed in packages/contracts.
Coordinator in the web app. It assigns threads to the six agent keys (priority, pinned, or most
recent, plus optional per-key pins) and maps their sidebar status to the device's colors. Command
keys run T3 Code keybinding commands by replaying the user's own shortcut, so rebinding and when
clauses keep working. Approve, decline, and stop go through the existing orchestration commands.
Settings → Codex Micro: a live preview of the device, connection, firmware and battery,
agent-key mode, per-key actions, knob mode, and brightness. The entry only shows while a device is
connected.
A user guide section in docs/user/.
How it fits the principles in AGENTS.md
Remote ready. Agent keys follow threads from every connected environment, not just the local
one. Actions go to each thread's own environment. It also works with the local environment turned
off, when the desktop app only talks to remote servers. feat(desktop): support the Work Louder Codex Micro #23869
only used the primary environment; fixing that was the main change I made.
Performance. HID enumeration is async and runs every 2s. The device only gets a lighting
write when the computed frame differs from the last one sent. No continuous animations: the device does its own breathing effects.
Native dependency.node-hid loads on first use, so a broken prebuild disables only the Codex
Micro and can never stop the app from starting. Packaging keeps only the target platform's
prebuilds.
Matches the sidebar. Subagent and side-chat threads don't take an agent key.
Platform notes
macOS needs Input Monitoring for the app. The guide covers this, and other input tools such as
Karabiner can interfere.
Linux needs a udev rule for 303a:8360. Windows needs nothing extra.
Only one app can own the device at a time, so Codex has to be closed.
Evidence so far
A real Codex Micro (firmware 0.6.2, USB) on macOS, with T3 Code 0.1.6 desktop connected to a remote
server, with the local environment both on and off. Detection, battery and firmware readout, agent-key
lighting, and the controls work. The protocol, slot-assignment, and action-mapping logic
have unit tests.
Not yet checked: Bluetooth, Windows, Linux.
Questions for maintainers
Is a desktop-only hardware integration in scope for T3 Code?
Is node-hid an acceptable dependency, given the lazy load and prebuild pruning above?
Should this be one PR (device link, coordinator, settings, docs), or a different split?
Related: #28252 asks for a keybinding command to start a side chat. Since the device's command keys run
keybinding commands, that would let a key start one too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
The Work Louder Codex Micro is a desk controller built for agent work: six
agent keys with status LEDs, seven command keys, a knob, and an analog stick. Codex's desktop app
drives it: each agent key follows a thread and lights up with its state (working, needs input,
unread, error), and the other controls approve, decline, stop, and so on.
In T3 Code the device does nothing. People who use T3 Code instead of Codex, or alongside it, have no
way to see agent state on the device or answer approvals from it.
Prior work
@Hormold implemented this in #23869. It was closed only because it lacked prior approval; there were
no technical objections. I've rebased that work onto v0.1.6 and I'm running it on macOS with a real
device. This discussion asks for approval of the direction and scope before a PR.
Proposed scope
Desktop only. The device is a local USB/Bluetooth HID peripheral, so web and mobile can't reach it.
The desktop app owns the connection and drives whichever environments it's connected to.
apps/desktop/src/codexMicro), usingnode-hidagainst the device's vendor interface (VID
0x303a, PID0x8360, usage page0xFF00). It speaksthe device's own newline-delimited JSON-RPC protocol: status, lighting config, per-key lighting,
key, knob, and stick events. It does not use Work Louder's SDK.
desktopBridge.codexMicrowithgetState,setLighting, andonEvent,typed in
packages/contracts.recent, plus optional per-key pins) and maps their sidebar status to the device's colors. Command
keys run T3 Code keybinding commands by replaying the user's own shortcut, so rebinding and
whenclauses keep working. Approve, decline, and stop go through the existing orchestration commands.
agent-key mode, per-key actions, knob mode, and brightness. The entry only shows while a device is
connected.
docs/user/.How it fits the principles in AGENTS.md
one. Actions go to each thread's own environment. It also works with the local environment turned
off, when the desktop app only talks to remote servers. feat(desktop): support the Work Louder Codex Micro #23869
only used the primary environment; fixing that was the main change I made.
write when the computed frame differs from the last one sent. No continuous animations: the device does its own breathing effects.
node-hidloads on first use, so a broken prebuild disables only the CodexMicro and can never stop the app from starting. Packaging keeps only the target platform's
prebuilds.
Platform notes
Karabiner can interfere.
303a:8360. Windows needs nothing extra.Evidence so far
A real Codex Micro (firmware 0.6.2, USB) on macOS, with T3 Code 0.1.6 desktop connected to a remote
server, with the local environment both on and off. Detection, battery and firmware readout, agent-key
lighting, and the controls work. The protocol, slot-assignment, and action-mapping logic
have unit tests.
Not yet checked: Bluetooth, Windows, Linux.
Questions for maintainers
node-hidan acceptable dependency, given the lazy load and prebuild pruning above?Related: #28252 asks for a keybinding command to start a side chat. Since the device's command keys run
keybinding commands, that would let a key start one too.
All reactions