npx pixel-agents fails: published npm package (1.0.2) is stale, has no bin entry

Summary

The published pixel-agents npm package (currently 1.0.2) is not the standalone CLI described in the README — npx pixel-agents fails outright. The published package appears to be a stale build of the VS Code extension bundle only.

Steps to reproduce

npx --yes pixel-agents --port 3100

npm ERR! could not determine executable to run

Root cause

The published package's package.json has no bin field at all:

{
  "main": "./dist/extension.js",
  "name": "pixel-agents"
}

(fetched via npm view pixel-agents / the registry metadata for 1.0.2)

Compare against the current source tree's root package.json (main branch, currently 1.3.0):

{
  "name": "pixel-agents",
  "version": "1.3.0",
  "bin": {
    "pixel-agents": "./dist/cli.js"
  }
}

The bin entry — and the whole standalone-CLI feature (server/src/cli.ts) — postdates whatever commit was published as 1.0.2. The registry version was never republished after the CLI landed, so npx pixel-agents / npm i -g pixel-agents cannot work today, even though the README's "Getting Started" section documents it as the intended zero-install path:

node dist/cli.js # or npx pixel-agents [--port 3100] after publish

Also note the published package's homepage points to github.com/pablodelucca/pixel-agents rather than github.com/pixel-agents-hq/pixel-agents — likely just a stale field from before the repo moved into the org, but worth fixing in the same republish.

Expected behavior

npx pixel-agents should start the standalone Fastify server + webview, per the README.

Suggested fix

Publish a new npm release from current main (or wire up CI to publish server's build output under the pixel-agents package name on tag/release), so the bin field and dist/cli.js are actually included in what npm view pixel-agents resolves.

Environment

• OS: Ubuntu 24.04.4 LTS
• Node: v22.0.0
• npm: 10.5.1