Pixel for Claude Code

pixel install adds lifecycle hooks to Claude Code’s user settings, so every session starts with Pixel’s protocol, and pixel install --repo adds an advisory guard to one repository.

Updated

Install Pixel

Pixel is a command-line tool: Claude Code runs the pixel binary, so install it first (macOS and Linux).

brew install LivioGama/tap/pixel

The install script is the other channel. Neither one changes any agent’s configuration.

What pixel install writes

pixel install

Run it once, from anywhere. For Claude Code:

  • ~/.claude/settings.json

SessionStart and UserPromptSubmit hooks in ~/.claude/settings.json inject the prompt as context, plus a PostToolUse hook on Edit and a SessionStart hook on compact. No shell wrapper, never blocks.

Every pixel install also deploys the prompt itself to ~/.local/share/pixel/agent-prompt.md and ~/.local/share/pixel/subagent-prompt.md, and wires the other agents it finds.

Or as a plugin

/plugin marketplace add LivioGama/pixel, then /plugin install pixel@pixel: its SessionStart and SubagentStart hooks inject the protocol instead.

The plugin never installs the pixel binary. The protocol it loads starts by checking for it (command -v pixel) and tells the agent to work without Pixel’s commands when it is missing.

Per repository

pixel install --repo .

Adds an advisory guard to this repository only, and skips every global step. For Claude Code:

  • .claude/settings.local.json
  • .claude/pixel-rtk-hooks.json

The guard steers the agent toward Pixel commands, for example with a notice before an untargeted read of a large source file, and never blocks a tool call. Every file that names this machine’s pixel binary goes into the clone’s .git/info/exclude, so a git add -A cannot publish it. Every per-repository file

Check it

pixel doctor .

pixel doctor . reports the wiring of every agent as green, stale or missing, and names the command that repairs each finding. For Claude Code alone:

pixel doctor . --only install.claude-hooks --only repo.claude-hooks

Remove it

pixel uninstall

It removes everything pixel install wrote, for every agent at once, and the binary at ~/.local/bin/pixel, where the install script puts it. A package manager removes its own copy: brew uninstall LivioGama/tap/pixel.

pixel uninstall --repo . removes only this repository’s files.

Measured

On one scoping task in Pixel’s own repository, Claude Code with Pixel took a median 30% less wall time than the same agent without it, over 11 runs per side (Claude Sonnet 5, Pixel 0.5.0, September 2026). That is one task on one repository: a direction, not a promise for yours. The runs, their spread and the cases where Pixel is slower

Pixel for other agents