Pixel for Pi

Install Pixel

Pixel is a command-line tool: Pi 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 Pi:

• ~/.pi/agent/APPEND_SYSTEM.md

~/.pi/agent/APPEND_SYSTEM.md, read automatically.

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

pi install git:github.com/LivioGama/pixel.

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 Pi:

• .pi/extensions/pixel-guard.ts

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

Pi loads the extension once it trusts the project.

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 Pi alone:

pixel doctor . --only install.pi-prompt --only repo.pi-guard

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.