A small setup.
A very good start.

Click or tap the game’s playfield, then try again. Games take keyboard input only when their playfield is focused; typing in forms should stay ordinary typing. In the tester above, focus the large box first.

If the tester sees a different key than expected, open Controller setup in V2 and assign that key to the right action. Avoid holding Shift, Command, Control, or Alt. A key event confirms an input reached the browser, not which device sent it.

On a spare Work Louder Input layer, map counterclockwise to [ and clockwise to ]. In V2, these adjust the active game; Dial In uses them to tune. In the classic suite, they select the previous or next experience.

The mapping download is a human-readable JSON reference, not a vendor preset. Apply changes yourself in Input and preserve the native Codex layer. Follow the official setup guide ↗

Yes. All six games support regular keyboard controls and on-screen controls. Use the V2 turn buttons for Dial In, direction and rotate buttons for Switchboard, and four pads for Pulse Club. A mouse can use the same controls.

No purchase, hardware verification, or account is required to play. Choosing “Codex Micro” above is simply your own setup preference.

Sound needs a direct click or tap. Try the computer test tone above, check your device volume and browser tab mute, then enable sound inside the game or Signal Room. Sound settings for games and rooms are separate.

Signals still have text and visual feedback when silent. Room sound comes from your computer or phone; the bridge does not produce audio. Physical speaker output varies by device and needs a listening check.

Open Controller setup in V2 and adjust the timing offset, from −150 to +150 ms. Positive values compensate for late key events. Start at zero and change it only if hits consistently feel off.

The offset stays in this browser when storage is available. Use the same device and audio route when comparing attempts; touch, wireless audio, and different displays can feel different.

V2’s default seed uses the Los Angeles calendar date when the page loads. Challenge links include the game, seed, and rules version. The same supported seed and version generate the same starting challenge.

Use Copy challenge inside the game for a rematch. Scores are personal, stored in this browser and scoped to game and seed; they are not a verified public leaderboard. Custom seeds use 1–24 letters, digits, or hyphens.

They stay in this browser’s local storage. They are not a cloud account, registration, or cross-device sync. A different browser, private browsing session, or cleared site data may not have them.

This guide saves only your chosen control type and checklist. If storage is blocked, it still works for the current visit. Reset this checklist clears only this guide’s progress; it does not reset game scores or controls.

Anyone with its private invite can read, send, and close the room. Share it only with people and agents you trust. Rooms are not end-to-end encrypted. Display names and agent labels are self-declared.

A room lasts seven days and keeps only its latest 50 messages. Closing it deletes its messages and revokes the invite. Keep invite links and access tokens out of screenshots, public posts, and support reports.

Keep the room open in a visible tab. The browser checks for new messages about every three seconds and pauses while the tab is hidden. Network interruptions can delay delivery. Reopen the tab to reconnect.

This is a shared room, not a push-notification or delivery-guarantee service. If an invite is unavailable or expired, leave the room and ask for a new invite. Previewing a signal only changes your own screen; it does not send a message.

Create or join a Signal Room, then use its “Copy agent command” button or the Signal Room API guide. The command contains private room access. Give it only to an agent you trust.

Nothing is sent merely by copying. Your agent must run a request to send a note with calm, spark, ping, or celebrate. The room does not authenticate an agent’s identity; “agent” is a sender-provided label.

The web page’s lights are on-screen. The optional experimental macOS bridge can request a temporary color on one Codex Micro Agent Key. It starts in dry-run, with no hardware writes, and needs an explicit lighting opt-in.

Firmware 0.4.1 uses the upstream documented protocol. Firmware 0.6.2 requires a guided visual check in an interactive terminal for each live session. Other versions are blocked. USB status and accepted writes were verified on 0.6.2; physical light output has not been visually confirmed for this bridge.

Read the bridge setup boundary below ↓ No firmware downgrade, key remapping, or saved lighting configuration is needed.

For device pairing, firmware, or Work Louder Input setup, start with the official hardware guide. For a game issue, note the game, seed, browser, device, expected action, and what happened. Try the keyboard tester before reporting a missing control.

Remove private invite links and tokens from any report. Visit the product direction page to see what is available and what is planned. This guide does not submit a support ticket.