pixel

Pixel for Claude Code

pixel setup registers Pixel’s hooks in Claude Code: each code prompt reaches the model with a source-cited evidence brief, and the pixel skill covers follow-up questions. Ordinary searches remain native.

Updated

Install Pixel

Pixel is a command-line tool: Claude Code 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. For Claude Code:

  • ~/.claude/settings.json

Hooks in ~/.claude/settings.json (task lifecycle, a prompt-submit evidence brief and a metrics relay) and the pixel skill in ~/.claude/skills/pixel/; foreign hooks are preserved and native search is untouched.

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: Claude Code keeps its native search, and Pixel’s commands stay available when you ask for them.

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

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.

Evidence and limits

An Opus 5.5 medium trial compared 11 runs per arm on one low-research scoping task. Median duration was 42.9 s without Pixel and 47.6 s with Pixel 0.5.0’s install hooks, which predate the prompt brief (+11%); median tokens read rose 12% and provider-reported API cost rose 31%. This is one task, not a general result for your sessions. Raw runs are not archived; known setup and provenance limits explain what can and cannot be checked.

Pixel for other agents