Developers
Start with pixel audit on your repository, then pixel list-signatures <file> on a file your agent often opens. The outline helps locate code; read the relevant bodies before editing. File/outline measurements describe the pinned sample and its parsing limits.
pixel scope-task suggests where to start, and pixel who-calls finds callers. Retrieval measurements cover the measured latency and caller coverage. Install the protocol once; your agent’s page explains how it receives it.
Lead developers
pixel impact lists callers and callees before a change; pixel review-changes shows a structured diff. A static graph can miss dynamic calls, so an empty result is not proof that a change is safe.
Git operations include leased pushes and pixel plan-rollback, which writes nothing until --apply. pixel install --repo adds project guidance and supported retrieval guards. Wiring and policy explain their modes and exceptions.
Harness engineers
Index answers carry completion markers and graph answers state their blind spots. Reading the answers explains how to consume them. The optional classifier uses a model and is separate from deterministic retrieval.
Pixel uses a CLI plus agent instructions and hooks. Context overhead and agent trials describe the tested harnesses: tool use is not proof of lower task time or billed cost. Use pixel action-log to verify adoption in your own sessions.
CTOs
The index stays in .pixel/, with no account and no telemetry from the binary. The security model names the downloads and optional network operations. Pixel is MIT licensed; compatibility lists the agents that can share the index.
The savings estimate applies file/outline volume rates to your own assumptions and input price. It does not predict a session’s invoice. Read the method and losses and alternatives before deciding.