Pixel Agents

Purpose: Managing, monitoring, and coordinating multiple Claude Code agents across projects without switching between terminal sessions.

Inferred · not functionally tested

Audience: developers using Claude Code across multiple projects

Inferred · not functionally tested

Functions: agents, collaboration, workflow_automation, analytics

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI, WEB · deployment: browser, cli, macos, windows, linux, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: mateovalle.github.io · github.com. These links do not verify the individual claims.

Pixel Agents sits in PulseGate's Other agents category. Inferred · not functionally tested: Managing, monitoring, and coordinating multiple Claude Code agents across projects without switching between terminal sessions. Inferred · not functionally tested: Pixel Agents is an open-source project aimed at developers using Claude Code across multiple projects. Basis unknown · not verified: Pixel Agents is open source under the MIT license. Basis unknown · not verified: It ships for the web, the command line, macOS, Windows, and Linux, and it can be self-hosted.

Behind Pixel Agents is Mateo Valle, and it first shipped in 2026. Development happens publicly on GitHub with 52 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are campus map, agent monitoring, and rich chat. Inferred · not functionally tested: Catalogued interfaces include a public API.

Summary written by a language model from the project’s public pages.