Skip to content

Releases: yoavmagor/wolfpack

v1.6.6-dev.wolfpack.1 — upstream main (unreleased) + fork patches

Choose a tag to compare

@yoavmagor yoavmagor released this 11 Jul 23:45

Fork build tracking upstream almogdepaz/wolfpack main @46f71d4 merged with this fork's customizations.

What "1.6.6-dev.wolfpack.1" means

  • 1.6.6 — the internal version on upstream main right now.
  • -dev — this is unreleased upstream work. Upstream's latest tagged release is v1.6.5 (2026-06-25); main is 37 commits ahead of it and has not been cut into a release. This build includes all of that unreleased work (e.g. direct CLI attach, agent status authority model, session identity restore, the Rust wolfpack-broker PTY architecture).
  • .wolfpack.1 — plus this fork's own patches, first revision.

Fork patches on top of upstream

  • Tailscale binding — server honors WOLFPACK_HOST; service install writes WOLFPACK_HOST=0.0.0.0 into the launchd/systemd unit when tailscaleHostname is set (fixes connection-refused over Tailscale).
  • CORS for raw Tailscale IP — allowlists http://100.x.x.x:<port> so phone/browser access over the raw IP works.
  • iOS PWA safe-area — header respects env(safe-area-inset-top) so the status bar no longer overlaps the nav buttons.
  • Image input — attach a photo from camera/photo library; downscaled (max 1568px, JPEG), saved under the session project's .wolfpack/images/, path inserted into the message input for the agent.

Assets (macOS only)

This is a source-built release for the two Macs this fork runs on — Intel (x64) and Apple Silicon (arm64). No Linux binaries. Each platform needs both the wolfpack binary and the matching wolfpack-broker (the broker owns PTY sessions in the current architecture).

File Platform
wolfpack-darwin-x64 + wolfpack-broker-darwin-x64 macOS Intel
wolfpack-darwin-arm64 + wolfpack-broker-darwin-arm64 macOS Apple Silicon

checksums-sha256.txt covers all four. Binaries are unsigned (ad-hoc) — clear quarantine and self-sign after download (see install steps).

Install / upgrade

Pick your arch (uname -m → x86_64 or arm64); example for Intel:

mkdir -p ~/.wolfpack/bin
curl -fSL -o ~/.wolfpack/bin/wolfpack \
  https://github.com/yoavmagor/wolfpack/releases/download/v1.6.6-dev.wolfpack.1/wolfpack-darwin-x64
curl -fSL -o ~/.wolfpack/bin/wolfpack-broker \
  https://github.com/yoavmagor/wolfpack/releases/download/v1.6.6-dev.wolfpack.1/wolfpack-broker-darwin-x64
chmod +x ~/.wolfpack/bin/wolfpack ~/.wolfpack/bin/wolfpack-broker
xattr -cr ~/.wolfpack/bin/wolfpack ~/.wolfpack/bin/wolfpack-broker
codesign --sign - --force ~/.wolfpack/bin/wolfpack ~/.wolfpack/bin/wolfpack-broker
wolfpack service uninstall && wolfpack service install

service install stages the broker next to the binary and installs both the server and broker launch agents.

v1.6.2 — iOS PWA safe area fix

Choose a tag to compare

@yoavmagor yoavmagor released this 02 Apr 09:59

What's new

Includes all upstream commits through v1.6.0 + the fixes from v1.6.1.

Fixed in this release

  • iOS PWA home screen: header obscured by status bar — The back and settings buttons were overlapping with the iOS clock/battery display when running as a home screen shortcut. Fixed by applying env(safe-area-inset-top) to the header (the right place), and removing a misplaced workaround that was adding dead space to the terminal view instead.

  • Tailscale binding (from v1.6.1) — Server now binds to 0.0.0.0 when tailscaleHostname is configured.

  • CORS for raw Tailscale IP (from v1.6.1) — Raw 100.x.x.x addresses are now allowed origins.

v1.6.1 — Fix Tailscale binding and CORS

Choose a tag to compare

@yoavmagor yoavmagor released this 02 Apr 09:45

What's fixed

  • Server binding: The service now correctly binds to 0.0.0.0 when tailscaleHostname is configured, restoring Tailscale access after the v1.6.0 refactor.
  • CORS for raw Tailscale IP: The server detects the local Tailscale IP at startup (tailscale ip -4) and adds it to the allowed origins, so accessing wolfpack via the raw 100.x.x.x address no longer returns 403 origin not allowed.

Both issues were regressions introduced in the almogdepaz#43 refactor. See PR almogdepaz#104 on the upstream repo.