Agent Keys for VS CodeShow up to 20 VS Code agent sessions on a Work Louder Creator Micro 2 or Codex Micro. Simply press the physical key to open the exact conversation. Each concurrent Copilot Agent session has a dedicated, color-coded status indicator you can act on without hunting through editor windows and tabs. Agent Keys is a desktop VS Code extension. No custom firmware is required. Just Keep Input.app running: it handles keyboard communication and continues providing your normal macros. Quick start
Key States
Detailed instructions and documentationInstall and configureRequires desktop VS Code 1.147 or newer, Work Louder Input.app v1.2.0 or newer, and a supported keyboard. The current AHP integration is intended for macOS desktop; browser VS Code and remote-only agent hosts are not supported.
No count is assumed on a fresh install. Until configured, AgentKeys does not connect to Input or allocate keys. Credentials are stored in VS Code SecretStorage. After revocation, the extension requests approval again; unsuccessful approval attempts are spaced at least one minute apart. Map API Smart Actions in Input
Identifiers are case-sensitive and zero-padded. The number identifies the slot, not the physical key position. You can position the keys freely. AgentKeys never reads or writes layouts, profiles, firmware, or ordinary key mappings. Input cannot enumerate your API mappings, so you must configure the count yourself. Sidebar and commandsThe sidebar shows Input connectivity, available AHP sessions, and each configured key's state and project. Hover a key for its full project path, session identity, last update, and error details. Click a bound key to open its conversation.
Reset and reconnect buttons are also in the sidebar toolbar. Reset is not the same as restart: reset remembers current turn identities so the same ongoing work does not immediately reclaim a key. New turns can bind again. Reloading VS Code preserves bindings and restores authoritative AHP state instead. Opening a green key acknowledges completion to white while retaining its shortcut. Opening a red key releases the failed binding only after successful URL launch. Active, waiting, and failed bindings are never evicted to make room for another session. Lifecycle and multiple windowsThe extension activates automatically after startup and runs while an enabled desktop VS Code window remains open, even when unfocused or with the sidebar hidden. One window owns the Input and AHP clients; other windows share the live status and forward commands. When the owner closes or reloads, a remaining window takes over. This is not a background OS service: monitoring pauses during sleep, extension-host restarts, and when all enabled windows close. Keys can retain their last colours while disconnected; the next owner restores their current state. Coordination uses an authenticated, loopback-only connection on port 19148. It is private extension IPC, not a supported scripting API. The OS socket bind ensures one owner; a hung owner is reported rather than bypassed by a second writer. Input itself uses port 19147. The key count, binding checkpoints, and private coordination token live in
The owner discovers AHP in its VS Code user-data directory, including custom
Remote SSH/container windows run AgentKeys on the local UI side, but that does not
make remote AHP sessions visible. Only sessions advertised in the selected local
registry are supported. AHP discovery and exact Migrating from the daemonStop and uninstall the old LaunchAgent before configuring the extension so it does not compete for Input lighting. In a normal macOS Terminal:
Remove its |