Repository navigation
0.10.0 — 2026-10-08
Release Notes
Added
- pando runs on Windows inside WSL 2, as the Linux binary, and knows
when it is there:pando openand the TUI'soopen Windows' browser:wslviewwhen
wslu is installed, otherwise Windows' own URL handler, found at
/mnt/ctoo when Windows' PATH is kept out of WSL. They used to
say they could not runxdg-open, which Ubuntu on WSL does not ship.pando doctortreats a tool found on a Windows drive as seriously as
a missing one. WSL puts Windows' PATH after Linux's, so with no Linux
npm the shell finds the script Node's Windows installer leaves, and
with no Linux docker the one Docker Desktop leaves. The fix says to
install the tool inside WSL, or to turn on Docker Desktop's WSL
integration.- It notes a repository, or a worktrees directory, on a Windows drive
(/mnt/c). git is several times slower there, and an edit sends no
file event, so dev servers do not reload. - When the Docker daemon does not answer, the fix names Docker
Desktop's WSL integration, and the distro's own docker service for
Docker installed inside it. - The TUI's copy keys fall back to
clip.exefor a terminal that
ignores OSC 52, for ASCII text, whichclip.execannot mangle.
Changed
- Everything pando asks of the operating system is behind one layer,
src/platform: process groups, signals, locks and permission bits, the
shell a command runs in, the boot, copy-on-write, and what the desktop
opens and copies with. Nothing else names an OS, and a test holds that.
On macOS and Linux one thing changes:pando update's install script,
andshare's check thatcloudflaredis on PATH, run in/bin/sh
rather than the firstshon PATH, asopen's commands already did. - A native Windows build compiles, and every command but
completions
stops at once with one line that says to run pando inside WSL 2: its
Windows backends are not built yet. CI builds it on Windows so they
keep compiling.
Fixed
- A WSL 2 distro, or a container, that restarted under a kernel that
kept running left pando trusting the pids it had recorded before. The
kernel's boot id stays the same through such a restart, sostatus
could call a dead dev server running, andstopcould signal another
process's group. On Linux the boot pando records now includes when
init started, which changes with every such restart. Worktrees that
are running when pando is upgraded are kept. - The test suite passes with a git older than 2.41, such as Ubuntu
22.04's, and on a WSL machine whose Windows side has npm or Docker
Desktop on PATH.
Install pando-cli 0.10.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.10.0/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.10.0
| File | Platform | Checksum |
|---|---|---|
| pando-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| pando-cli-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| pando-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| pando-cli-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo mertkaradayi/pandoYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo mertkaradayi/pando