Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Finding / heypi

2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-release

heypi 0.3.0-beta.2 remains the install channel without a new release. No heypi source commit, tag or package publication was found in the window. All six packages still advertise beta.2 as latest. Core declares Node >=22, but a fresh resolution of Pi 0.79.10 declares >=22.19.0; the Gondolin adapter still declares >=23.6 and needs QEMU. npm create heypi@latest -- codex-tag my-agent copies the one Codex Tag template and installs its dependencies, with no adapter/runtime/model interview. The template selects Docker, a bash command policy and loopback admin, always starts a local adapter, adds Slack only when both credentials are supplied and forwards a GitHub token only if supplied. Pi owns model execution/transcripts/tools/session state; heypi owns transport/policy/staging/coordination. It is a supervised Node process with file-backed state and a one-process-per-state-directory deployment contract. The 0.3 rewrite is intentionally incompatible and removed its migration path.

Channel: preview-or-beta npm latest and tag; no main-only heypi changes; legacy non-prerelease 0.1.3 is separate. Half: both. Date: 2026-07-22 (beta.2 publication); channel rechecked for the 2026-10-13 cutoff on 2026-10-14.

Operator consequence: Pin @hunvreus/heypi@0.3.0-beta.2 or create-heypi@0.3.0-beta.2 explicitly for a new evaluation, inspect the selected runtime and generated policies, and keep the consumer lockfile. The old 0.1.3 remains installable but is not the recommended starting point for a new deployment; its older defaults are not beta.2 defaults. Rebuild 0.2.x configurations rather than assuming a migration. Package and dependency activity, not guesses about maintainer intent, should guide operational planning.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-release

Profile citations

  • heypi / claim / governance-shell-built-on-pi
  • heypi / claim / single-host-node-service-deploy
  • heypi / claim / tags-only-no-github-releases
  • heypi / claim / beta-channel-and-single-template
  • heypi / posture / capability
  • heypi / posture / accessibility

Source links

Primary links, including exact changelog lines when available.

  1. heypi
    official docs2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releaseregistry.npmjs.org/%40earendil-works%2Fpi-coding-agent/0.79.10official docs2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releaseregistry.npmjs.org/%40hunvreus%2Fheypiofficial docs2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releaseregistry.npmjs.org/create-heypiofficial docs2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releaseapi.github.com/repos/hunvreus/heypi/git/tags/7e126ec748a66db9cd854c2474f630af60a64cbegit compare2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasegithub.com/hunvreus/heypi/compare/0.3.0-beta.2...maintagged commit file2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasehunvreus/heypi / packages/heypi/docs/reference/cli.md#L13-L20tagged commit file2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasehunvreus/heypi / examples/codex-tag/index.ts#L7-L35tagged commit file2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasehunvreus/heypi / packages/heypi/docs/guides/deployment.md#L3-L24tagged commit file2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasehunvreus/heypi / CHANGELOG.md#L3-L63tagged commit file2026-10-13-heypi-heypi-0-3-0-beta-2-remains-the-install-channel-without-a-new-releasehunvreus/heypi / packages/heypi/docs/reference/architecture.md#L3-L19