Claude Code Keypad — Development skill for Claude Code

claude-code-keypad

Live Claude Code session status on the keys of a [Work Louder Creator Micro 2](https://worklouder.cc).

Each key is one of your running sessions, coloured by what it is doing. Press a key to jump to that chat.

Setting it up with an agent

Paste this to Claude Code, or any agent with shell access, and it will do the whole thing:

Set up my Work Louder Creator Micro 2 to show Claude Code session status on its keys.

Run: npx github:00cyre/claude-code-keypad install

It will ask which layer to use and map that layer's keycodes itself. Before you
answer, tell me which layer you are picking and which of my existing macros it
will unbind — it prints both. Do not pass --yes; I want to see the plan.

If anything fails, run `npx github:00cyre/claude-code-keypad doctor` and tell me
what it says rather than guessing.

It backs the keymap up to `~/.claude-code-keypad/backups/` before changing anything, and prints the path.

Install

One command. It fetches the package, compiles the native HID bridge, installs a login item, and starts it:

npx github:00cyre/claude-code-keypad install

That is the whole setup — it runs from now on, comes back at login, and restarts if it crashes.

npx github:00cyre/claude-code-keypad status      # running? up to date?
npx github:00cyre/claude-code-keypad update      # fetch the latest, same options
npx github:00cyre/claude-code-keypad uninstall   # stop it, remove the login item

**It does not update itself.** `install` puts a frozen copy in `~/.claude-code-keypad`, and that is what runs until you say otherwise. `status` checks GitHub and tells you when a newer commit exists; `update` reinstalls with exactly the options you installed with, so a `--layer` or colour you chose is not lost. Each machine is separate — updating one does nothing to another.

Options after `install` are baked into the login item, so that is where to set your defaults:

npx github:00cyre/claude-code-keypad ins