pixel

Pixel for Pi

pixel setup adds a local Pi package: the explicit /pixel-impact <symbol> command, a hook that adds a source-cited evidence brief to each prompt and a relay of the metrics line, plus the pixel skill for follow-ups. Pi keeps its native tools.

Updated

Install Pixel

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

curl -fsSL https://github.com/Pixel-CLI/pixel/releases/latest/download/install.sh | sh

How to read the script before it runs. It does not change any agent’s configuration.

What pixel setup writes

pixel setup

Run it once, from anywhere; it writes Pi’s files when Pi's agent directory ($PI_CODING_AGENT_DIR, else ~/.pi/agent) exists or pi is on PATH. For Pi:

  • ~/.local/share/pixel/pi-package/package.json
  • ~/.local/share/pixel/pi-package/extensions/pixel-impact.ts
  • ~/.local/share/pixel/pi-package/extensions/pixel-brief.ts
  • ~/.pi/agent/settings.json
  • ~/.pi/agent/skills/pixel/SKILL.md

The local package provides /pixel-impact and a before_agent_start hook that runs Pixel's prompt-submit hook on the submitted prompt and prepends its bounded evidence brief, and a tool_result hook that shows the metrics line after a pixel bash call; the pixel skill sits in ~/.pi/agent/skills/pixel/; Pi's native tools remain unchanged.

Every pixel setup also writes ~/.pixel/setup-receipt.json and ~/.pixel/config.yaml and ~/.claude/skills/pixel/SKILL.md and ~/.config/opencode/skills/pixel/SKILL.md and ~/.gemini/skills/pixel/SKILL.md and ~/.pixel/plugins/cand-j-callers/ and ~/.pixel/plugins/cand-j-chain/ and ~/.pixel/plugins/cand-j-stop-cause/ and ~/.pixel/plugins/cand-k-code-sites/ and ~/.pixel/plugins/cand-k-commit-patch/ and ~/.pixel/plugins/config-registry/ and ~/.pixel/plugins/doc-sections/ and ~/.pixel/plugins/error-origin/ and ~/.pixel/plugins/flow-rank/ and ~/.pixel/plugins/history-fallback/ and ~/.pixel/plugins/name-files/ and ~/.pixel/plugins/overview-answer-evidence/ and ~/.pixel/plugins/rank-blocks/ and ~/.pixel/plugins/test-bodies/. No prompt, rules file or retrieval guard is written: Pi keeps its native search, and Pixel’s commands stay available when you ask for them.

Your other Pi settings and packages stay: Pixel adds only its package path to packages, and pixel setup --remove takes it out again.

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-impact

Remove it

pixel setup --remove

It removes everything pixel setup 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: uninstall with the manager that owns it.

Pixel for other agents