This page gives direct, citable answers to common questions about a Work Louder Input CLI, Codex Micro configuration, and AI-assisted macropad automation.
WorkLouderCTL is an open-source full-configuration CLI for Codex, Work Louder Input, and Codex Micro. It targets every Codex Micro configuration surface exposed by both GUIs.
WorkLouderCTL fills that role. The source-built CLI reads
Codex settings, Input cache state, and live Codex Micro status/files through
Input 0.18.0's bundled provider. It also generates strict offline candidates
and runs authenticated Codex/Input apply/readback/restore/rollback transactions
against isolated reference writers. The exact-release overlays for Codex
26.730.61309 and Input 0.18.0 are version/hash gated, and provider
acquisition requires a real RPC response. Signed, notarized Apple Silicon and
Intel packages are published through GitHub Releases and the stable Homebrew
tap.
Run worklouderctl doctor --strict to test the current machine rather than
inferring write support from installed/running apps. The JSON field
configurationReady becomes true only after both authenticated bridges
advertise all required apply and restore capabilities. A plain doctor remains
read-only and reports an unavailable bridge as a warning.
The provider lifecycle is also available through the binary:
worklouderctl provider install codex
worklouderctl provider install input
worklouderctl provider status
worklouderctl doctor --strictDevice and transaction commands default to --owner auto. When Codex is the
owner, device configuration takes a serialized Input lease and restores Codex
after success or failure. An explicit provider handoff remains available.
These commands replace direct use of the repository's Node helper entrypoints.
Every setting available in the Codex Micro page or Input's Codex Micro views gets a typed CLI command and JSON representation. Codex and Input may remain running as execution engines, while configuration no longer depends on using their GUIs.
It replaces their Codex Micro configuration workflows. Codex still executes Codex-aware commands and task lighting; Input still executes Smart Actions, Cheat Sheet, transport, firmware updates, and other host behavior. AppSense can use Input's runtime or the CLI's Codex-owner macOS focus relay. The project does not replace those runtimes or the hardware driver.
Codex and Input updates can add transport fixes, firmware support, device capabilities, and runtime behavior. WorkLouderCTL detects and delegates to the installed providers instead of maintaining a second driver stack. The CLI owns configuration automation and verification while upstream owns device/runtime evolution.
Work Louder Codex Micro on macOS is the verified target. Codex 26.730.61309 and Input 0.18.0 are the current exact-release adapters; Input 0.17.3/0.18.0 and Codex Micro firmware v0.6.0 remain the sanitized fixture boundary. New versions enter capability discovery before writes are enabled.
The complete model includes Codex-native Agent/Command keys, voice, Codex dial, Codex joystick, and task-state lighting in Tier 1. Input-backed tiers include profiles, six layers, the key matrix, encoder, joystick sectors, Actions, Multi Actions, Smart Actions, linked apps, backlight, underglow, and layer metadata. The CLI configures every tier through its corresponding authority.
Global Codex lighting brightness and auto-off are already available as strict
offline codex lighting brightness/auto-off get/set candidates. The isolated
Codex bridge E2E applies both fields, reads them back exactly, and restores their
baseline values through the complete settings transaction.
The voice button also has typed codex voice get/set candidates for
push-to-talk and realtime (Voice Chat). The editor preserves future layout
fields and the bridge fixture restores the exact baseline mode and source hash.
Yes, through the deterministic JSON contract. Human and agent clients share the same transaction model: inspect, plan, diff, apply, verify, and rollback. There is no separate unverified AI write path.
Yes. The source-built CLI snapshots all six AG00-AG05 assignments, reads or
edits one slot offline, supports command, Skill, task, keycap, and empty values,
then applies or restores the complete object through the Codex Companion Bridge.
The transaction uses a canonical global-state revision, immutable backup,
idempotent retry, stale-state rejection, exact readback, and automatic rollback.
Selecting those custom assignments remains a separate explicit
codex-micro-agent-source=custom settings transaction.
The safety contract requires:
- fresh reads of every authority;
- immutable private backups;
- validation and reference checks;
- an exact user-visible diff;
- conflict detection immediately before writing;
- dependency-safe file order;
- byte/JSON readback and checksums;
- automatic rollback after a failed mutation;
- a runnable manual restore command.
The Input Companion Bridge keeps Input as the only owner of the device session. CLI requests enter Input through a private authenticated Unix socket and use the same service container and serialized device queue as GUI requests.
Write capabilities are advertised only when that Input version injects a verified complete-configuration writer. The CLI then takes an immutable backup and Input performs CAS, idempotent apply, full readback, and automatic rollback inside the same serialized bridge session.
Input 0.18.0 does not ship the listener itself. The version- and hash-gated
live overlay attaches to its main process without activating or navigating the
GUI. On the tested macOS 27 beta, provider handoff uses a fresh hidden Input
process because restarting the released node-hid worker in place is unstable.
The direct compatibility transport retains require-closed and explicit
restart modes as read-only fallbacks.
The Codex Companion Bridge keeps the running Codex main process authoritative.
It delegates settings/global-state reads to Codex and advertises each mutation
capability only when Codex injects the corresponding exact complete-object
replacer. Settings use source-SHA plus settings-revision CAS; Agent Keys use a
separate global-state revision CAS. Both paths provide immutable backup, exact
readback, restore, and rollback over a private authenticated Unix socket. The
current Codex release contains the internal handlers but does not ship the
external listener. The version- and hash-gated live overlay installs the same
contract without focusing the GUI; settings and Agent Keys have completed live
apply/readback/exact-restore transactions on the earlier Codex boundary; the
current schema and overlay are pinned to Codex 26.730.61309.
Smart Action text, command, URL, and app definitions, groups, references,
bindings, and delete cascades are implemented as strict offline candidates.
The released Input 0.18.0 overlay has live-validated its complete negotiated
configuration transaction, including the provider-owned database writer.
macOS is first because Input coordination and hardware evidence already exist there. Linux and Windows will follow transport and state-adapter milestones rather than being claimed before verification.
No. WorkLouderCTL is an independent community project. Product names are used only to identify compatibility targets.
See Configuration parity matrix and Compatibility and support policy.