Pixel for OpenCode

pixel install puts Pixel’s protocol into OpenCode’s global AGENTS.md, the one instruction file both OpenCode generations load.

Updated

Install Pixel

Pixel is a command-line tool: OpenCode 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; it writes OpenCode’s files only when OpenCode's config directory exists: $XDG_CONFIG_HOME/opencode, else ~/.config/opencode. For OpenCode:

  • ~/.config/opencode/AGENTS.md

The prompt appended to AGENTS.md.

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.

Your own instructions in that AGENTS.md stay: Pixel owns only the block between its pixel:managed markers. When the file does not exist yet and ~/.claude/CLAUDE.md does, the new file starts with that content, since on OpenCode's first generation a global AGENTS.md takes the place of the CLAUDE.md fallback.

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

pixel doctor . --only install.opencode-agents-md

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 for other agents