Repository navigation
Releases
0.11.2 — 2026-10-31
Release Notes
Added
clonetakes a Rust crate'starget. pando proposes it beside a
Cargo.toml(a Maven or sbttargetis left alone), and a new
worktree starts with the main checkout's build, copy-on-write: its
dependencies' fingerprints name no path of the checkout, so cargo
finds every one fresh and builds only the workspace's own crates,
where before each worktree built every dependency again on disk of
its own.pando checksays what a worktree costs on disk, for any project:
the gitignored trees its install and processes built from nothing,
each marked when the main checkout has oneclonecould share, and
the space the tools took outside it, such as a build cache keyed by
the checkout's path that fills again for every worktree. It prints a
line, andcheck --jsonhas it asdisk. pando judges none of it:
the agent brief says how to read it — which trees are safe to clone,
how to find a tool's setting that makes its cache independent of the
path and give it to the process through itsenv— and to check
again to see the difference.- The TUI takes the mouse. A click selects a worktree, a dialog's
option or a line of the log viewer, and a second click is⏎on it;
a click on a key hint presses its key,esc cancelcancelling; a
click on a tab of the log viewer, or on a process the log preview
names, shows that log; the wheel scrolls what is under the pointer.
Help lists all of it. Hold shift to select text while pando has the
mouse (option in iTerm2);[ui] mouse = falsein
~/.pando/config.tomlleaves it to the terminal, and the setup
screen always does, so its prompt can be selected and pasted. scripts/dev new, for contributors: a branch's worktree starts with
the main checkout'starget, cloned copy-on-write, so it builds only
pando and none of its dependencies again. Only ever a clone: on macOS
only where both sit on one APFS volume (cp -cwould copy
elsewhere), on Linux only as a reflink; otherwise cargo builds from
nothing, as before.scripts/dev use release, for contributors:pandois the release
you installed again, Homebrew's or the install script's, after
use <branch>made it a branch's build.pando updateon a branch's
build names it, andscripts/dev rmof the branchpandoruns goes
back to the release rather than to the main checkout's build.pando rmtakes several worktrees:pando rm feat/a feat/b fix/c
removes them side by side, says each as it finishes, and exits 1
naming any it could not remove;--yesand--forceapply to each.
One name reads exactly as before.pando start,stopandrestarttake several worktrees too:
pando start feat/a feat/bsettles every question first, one name
after another, then starts them side by side, each said as it
finishes; one that fails leaves the others, and the exit code is then- A question still open is the whole command's exit 3, and nothing is
started. Every flag applies to each; one name, or none, reads exactly
as before.
- A question still open is the whole command's exit 3, and nothing is
- Marks in the TUI:
+marks the row under the cursor, or unmarks it,
and moves down. A marked row has a+before the cursor's column,
and the list's title and the footer say how many are marked. A mark
stays on its worktree through a refresh, a re-sort or a filter, and
goes with it; esc unmarks every row, after clearing a filter. dwith rows marked removes every marked worktree from one dialog.
It lists each with what its removal stops or takes with it, says
which onlyFremoves (uncommitted changes) and which stay (locked,
the main checkout), and one confirm starts every removal at once.
ykeeps the ones that needFmarked, sodthenFfinishes
them.s,xandrwith rows marked start, stop or restart every marked
worktree at once, each on its own worker.xandrask for their
second press once for the whole set, while any of it runs; a marked
worktree that is up already, or busy with something else, is left
alone and said once. The other keys still act on the row under the
cursor.xon a worktree being started or restarted in the TUI cancels it,
where it saidalready busy starting …and a start could wait a
minute for a service. The start stops at its next safe point — a
readiness wait looks every quarter second, a hook already running
finishes first — through the undo a failure there runs, and the
worktree ends stopped.qtwice with a start in flight cancels it
and quits once it is undone, rather than leaving it half up;q
again quits at once.- The TUI shows a worktree another pando is removing —
pando rmin
another pane — as◌ removing, as it shows its own, ands,x,
r,dand sharing leave it alone, saying it is being removed. One
whose removal was stopped half way readsrm interrupted: nothing
starts it, anddfinishes the removal.
Fixed
pando updatesaid the update failed when Homebrew upgraded pando and
then exited 1 over something else: its periodicbrew cleanup, which
runs after the upgrade, refuses a cask from an untrusted tap. Whether
the update happened is now read from the installed pando's version, so
it reports the new version and says that what failed came after.- A panic in the TUI no longer leaves the terminal reporting focus
changes, which the shell then printed as^[[Iand^[[O. ls,status,open,start --waitand the TUI no longer wait for
another pando's lock: while armor astopheld it — adocker compose downcan take minutes — they printed nothing, andpando
opened onto nothing, until it let go. They now answer from the state
as it stands. A command that does have to wait sayswaiting for another pando to finishafter a second, rather than looking hung,
and the socket scan behind every read no longer holds the lock.pando stop --alland the TUI'sXstop every worktree at once:
one after another, each dev server slow to stop took its own five
seconds' grace, under the lock every other command waits for — four
of them, twenty seconds; now five. Their compose projects are asked
to stop together too.- A
pando stopno longer holds the lock while its processes take
their grace period to end, so two stops of two worktrees — the TUI's,
or two panes' — end together, and a refresh or a start of another
worktree never waits behind one: two worktrees whose servers ignore
SIGTERM stop in 5.3s at once, from 10.3s. A process a stop is taking
down is never shown as failed while it waits, nor a native database
it is stopping said to have exited, and a start of the same worktree
waits for the stop, says so, and then starts it fresh.restart,
stop --alland the TUI'sXstop the same way. - A folder of repositories is read one repository at a time no more:
its listing on every refresh and the TUI's first frame, its branches,
its pull requests, each set's git status, and each repository's base
fornew(a fetch, sometimes) are asked of every repository at once.
On six repositorieslstakes 0.15s, from 0.57s, and the TUI shows a
set's status as soon as its own repositories have answered. pando checkandpando newstop their install when they are told
to stop. A Ctrl-C that landed just before the install started, or a
killof pando alone — an agent's, CI's — reached pando and not the
install, and the check sat until the install ended by itself. Now no
hook starts once pando has been told to stop, and outside a terminal
a running one leads a process group of its own, which pando stops.- Removing a worktree no longer holds up every other command.
rm
stops what runs and marks the worktree as being removed under the
state lock, then takes its containers, its tree and its namespaces
down without it, so several removals — from the TUI, or from several
terminals — run side by side, and nothing else waits for one. A
worktree being removed refuses a start, a share, a secondrmand a
newof its name; a removal stopped half way, by Ctrl-C or a crash,
is finished by the nextpando rmof it, containers and namespaces
included. rmof a running worktree stops it asstopnow does, waiting for
its processes without the lock: two removals of worktrees whose
servers ignore SIGTERM end in 5.3s together, from 10.3s.unshareno longer holds every other command up while the tunnel and
its proxy get their five seconds to exit; the share stays recorded
until both are down.- The TUI no longer removes one worktree at a time:
don another
while one was being removed saidalready busy removing …. A removal
keeps the branch and writes no ref, so it runs beside another
removal, a new worktree being made, or a git move elsewhere. - A worktree being made in the TUI holds up git moves only while git
checks it out, not through the minutes its install takes, andX
goes ahead while one is being made: a create starts nothing a stop
of everything would stop. A create beside another's install no
longer fails when that install holds the repository's config a
moment (husky installsettingcore.hooksPath):newtries git's
lock errors again for up to three seconds.
Install pando-cli 0.11.2
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.11.2/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.11.2
| File | Platform | Checksum |
|---|---|---|
| pando-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | [checksum](https://github.com/mertkaradayi/pando/releases/download/v0.11.2/pando-cli-aarch64-... |
0.11.1 — 2026-10-26
Release Notes
Added
reposinpando init --answers:{"repos": {"members": [...], "base": {"<repository>": "<branch>"}}}writes a multi-repo project's
[repos], checked against the folder first, so a base only one
repository has can be answered. Abaseanswer some repositories lack
is refused naming them.signalspublishesenv_examples: every env example read, whole,
under its path.- The first-run setup knows a folder of repositories.
pando init --agentthere says the job is a set of worktrees, that a path names
its repository first, which repositories it reads no app in, and how a
repository takes a base of its own; run inside a repository of a
folder pando already runs, it says so. The brief gains a worked
example of the shape. pando newof a set that lacks a repository's checkout — lost, or of a
repository that joined the project since — adds just that checkout,
leaving the others and their work as they are.pando statuslists each repository of a set with its checkout's
branch, and names a process by its repository:api (backend).pando logs --source <repository>reads the logs of the processes in it.- The TUI says which repository a process, a log tab and a commit are
of, keeps a row for a checkout a set lacks, names the dirty
repository in the remove dialog, lets the create dialog come back to
each repository's own base, and welcomes a folder of repositories as
one.
Fixed
- A folder of repositories, or a repository whose apps sit in sibling
directories: one app'sPORTis no longer proposed as the project's
port_env, an app's own references reach that app alone, and a key a
second app also declares is no longer lost. - An app is told where a sibling listens when the sibling's port is only
in its code (process.env.PORT || 3001) or the reference only in the
app's own gitignored.env. - An app directory with a
startscript and no dev script is offered,
running it, instead of being left out. - The worktree's URL goes to the app that serves pages rather than an
API that sorts first: the API's table sayspage = false. - A
pagein an answered process table is written. - A multi-repo project's services: a compose file at a repository's root
(infra/docker-compose.yml) is proposed and run, and an isolated start
reads the address it rewrites from the repository that keeps it,
where it failed on every such project. Every directory's real env file
now speaks before any directory's example. - doctor reports a repository whose origin/HEAD is far behind its main
checkout's branch, with the[repos.base]line that fixes it.
Install pando-cli 0.11.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.11.1/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.11.1
| 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/pando0.11.0 — 2026-10-26
Release Notes
Added
- Projects split across several git repositories (#18).
pandoin a
plain folder of sibling repositories runs it as one project, and its
worktree is a set: a directory laid out like the folder with a worktree
of each repository on one branch, which every repository takes where it
has it and forks from its own base where it does not.startruns
every process of the set in one port window, so a frontend's process is
told its backend's port;stop,rm,status,open,shareand
checkact on the whole set, and the TUI shows it as one row with each
repository's branch and changes in its detail. The pull request picker
lists every repository's, each named with its repository. A configured
path names its repository first (provision = ["backend/.env"]), and
is checked against that repository's own gitignore.[repos] members
narrows which repositories are in the project, and[repos.base]sets
one's base.ls --jsonaddsproject.reposand each entry'srepos.
The git menu opens on one repository's checkout of a set, against
that repository's base, andtabgoes to the next.
Install pando-cli 0.11.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.11.0/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.11.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/pando0.10.3 — 2026-10-14
Release Notes
Fixed
- The TUI runs actions on different worktrees at once. A worktree that
was stopping used to refuse a start of any other with "already busy",
and two worktrees could never start together; now each worktree has one
action in flight, beside any other's. A stop-all still runs alone, and
creating, removing and the git menu's moves take turns, since they
write the repository's refs. Questions from two starts are asked in
turn; the second used to cancel the first. - A pull request merged or closed on GitHub shows in the TUI without
reopening it. pando asks GitHub again about once a minute, when its
pane gets the focus back, after a shell or editor from!ore, and
after a move from the git menu. AnRpressed while a fetch is out is
no longer dropped, nor is a re-read of git state asked for while
another runs;Rre-reads git state too. stop,restartand a stop-all wait for a worktree's processes to
end all together rather than one after another. The wait is under the
project's lock, so a dev server slow over SIGTERM held up every other
worktree's start, and the TUI's refresh, for up to five seconds per
process; now it is as long as the slowest.
Install pando-cli 0.10.3
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.10.3/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.10.3
| 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/pando0.10.2 — 2026-10-09
Release Notes
Added
space pin the TUI opens the selected worktree's pull request on
GitHub, the one its row's#nnames, open, draft, merged or closed,
running or not. The footer offers it on a row that has one; on a row
without, it says why: no pull request, no branch, or noghto ask.
Install pando-cli 0.10.2
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.10.2/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.10.2
| 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/pando0.10.1 — 2026-10-08
Release Notes
Changed
- A placeholder in a command a process, hook or probe runs is quoted for
where it stands: bare, inside double quotes, or inside single quotes.
A path with a space is one word, and a fork's branch namedx$(…)is
text, not a command. A plain value renders as before, andenvvalues
are not commands and stay as they are. .env.localis read before.env, as Next, Vite and dotenv-flow read
them, so pando finds the database and login the app really uses.- In namespaced mode each database the main checkout uses gets one of the
worktree's own.DATABASE_URL'sshopandTEST_DATABASE_URL's
shop_testused to become oneshop__<worktree>, so a test suite that
emptied its test database emptied the worktree's dev data.
Fixed
-
Namespaced mode tells a Redis slot it gave out from the same number on
another Redis answering on the same port. Each slot is marked as the
worktree's, and pando keeps which server process it was on.rmno
longer empties, and a start no longer writes into, another server's
slot. A slot recorded before this is trusted as before. -
Namespaced mode never makes or runs on a database that another
project's state records, such as a second clone of the repository on
the same server. -
The git menu no longer loses an ignored file such as
.env. A pull,
rebase or merge onto a base that has started tracking that path used
to replace it, and the abort after a conflict deleted it. Such a move
is now refused before anything runs, naming the files. -
The git menu moves a branch onto the base it was made from. That is
the branchnew --baseforked it from, or, for a pull request, the
branch the pull request targets. It used to rebase onto the
configured base: a branch cut fromreleaseand rebased ontomain
took every commit ofreleasewith it. -
The git menu refuses a move when
git statusdoes not answer, rather
than reading the tree as clean. Its fetches get five minutes, not
thirty seconds. -
A fork's pull request is fetched from the remote of the repository it
was opened against, such asupstream. Fetching fromorigin, a
contributor's own fork, could check out a different pull request with
the same number. -
pando rmdrops nothing in namespaced mode while it cannot read what
the main checkout's env files name today. Before, an unresolved value,
a renamed service or a moved port meant it decided on the record alone. -
Namespaced mode runs a worktree only on a database pando made. One
that was gone and was made again by something else, between pando's
check and its create, is refused rather than taken over. -
Namespaced mode reaches a server named by an IPv6 address
(postgres://…@[::1]:5432/shop). The clients used to be handed the
address in brackets, which they cannot resolve. -
pando doctornever offers to drop a database that a main checkout
names, even when the name looks like a worktree's. -
Namespaced mode finds a database container whose port on the host
differs from the port inside it (5433:5432). Docker's--filter publish=matches the inside port, so pando used to find nothing. -
The share proxy logs in only requests for the tunnel's own host. A web
page or another process reaching its loopback port directly is
answered421and never gets the session cookie. -
A shared event stream or long poll that is quiet for more than a
minute is no longer cut off. The proxy's upstream deadline now ends at
the first byte of the answer. The header deadline now covers the whole
header block, not each read. -
A Ctrl-C during
pando check's install or start records the check as
interrupted, not as failing settings. -
A Ctrl-C while
newclones files copy-on-write now stops it before
git writes the rest of the checkout and before thepost-checkout
hook runs. -
A port held by a listener on
[::]withIPV6_V6ONLYis no longer
handed out as free. uvicorn's--host ::and nginx'slisten [::]
listen like that. -
A process whose whole group had already exited when it was seen to
fail is never signalled later. That pid may by then belong to
something else. -
The state file is synced to disk before it replaces the old one, so a
crash right after a save cannot leave it empty. -
pando updatedownloads the install script into a new file only you
can write, not to a predictable path in the shared temporary
directory. Pre-release tags are ordered as semver orders them
(rc.10afterrc.9). -
The TUI saves the list's order and the theme when
uiin the config
is an inline or dotted table. It used to report success and write
nothing. -
A workspace member excluded with a negated glob, such as
!apps/legacy, is no longer proposed as an app.
Install pando-cli 0.10.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.10.1/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.10.1
| 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/pando0.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/pando0.9.0 — 2026-10-05
Release Notes
Added
- Namespaced mode for engines whose namespaces are the app's own: an
Elasticsearch or OpenSearch index, a Kafka or Redpanda topic, a
Meilisearch or Typesense index, a Memcached or Redis key. Where the app reads a prefix beside the
address (ELASTICSEARCH_INDEX_PREFIX,REDIS_PREFIX), a namespaced
worktree is told one of its own — main's, then the worktree's name and
a short hash of it and the project,feat_x_1f3c4a__— and the
service is its data. A prefix is told, never made: nothing is recorded
or dropped, andrmsays what it leaves. Every process of a
namespaced worktree is toldPANDO_NAMESPACE, the same name. - A database in a container is set up with nobody asked: where the
app's login may not make the worktree's database, pando runs the
grant it used to print as the container's own administrator, read
from its environment (POSTGRES_USER/POSTGRES_PASSWORD,
MARIADB_ROOT_PASSWORD,MYSQL_ROOT_PASSWORD), and where the app's
env files carry no login, that administrator is the login, the one
rmthen drops as. Only a container that alone publishes the port on
this machine's loopback, with nothing else listening there, is taken
for the server, and an administrator is used only once it answers. A recipe says where with
[namespace.container_admin]andrun_sql. - The setup brief's first run answers
namespacedwheninitsays a
service would stay on main's data. - A server in a container is reached through the client its image
ships: when the host has nopsql,mariadborredis-cliand a
container publishes the server's port, the recipe's commands run in it
throughdocker exec, the password passed by name. namespaced, the twelfth answerinit --answerstakes: per service,
the recipe its engine is, the keys its app names its database or slot
by, and the keys it reads a prefix from, written to
[namespaced.<service>]in pando's own file beside any login. Only a
program answers it; nothing asks a person.signalslists what a
namespaced start would do with every service, an undeclared compose
service included, and why one stays shared.[namespaced.<service>] recipeandprefix_env, besidedb_env; none
is a secret, so a committedpando.tomlmay carry them.- A recipe may say only how a server somebody else runs is namespaced: a
[namespace]or[prefix]with no[service], for an engine only a
compose file runs.
Changed
- Where an app names its database or slot is a recipe's
[namespace.address]— a URL's path and query parameters, and the
keys beside the address — rather than code; a recipe without one means
its kind's conventions, as before. Every address key's own slot key is
now found: two Redis roles with their own_DBkeys both move to the
worktree's slot, where the second went on naming main's. - A slot's
sizeprints a bare number; Redis's recipe passes--raw.
Install pando-cli 0.9.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.9.0/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.9.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/pando0.8.3 — 2026-10-05
Release Notes
Added
cloneis the eleventh question: detection proposes the gitignored
node_modulesthe main checkout has, the root's and each app's, so a
new worktree clones them copy-on-write before its install instead of
installing from nothing. Decided, sonewtakes it in a project set up
before it and says so; not offered when the install deletes the tree
first (npm ci).--answerstakes it as a list, andnullwrites
clone = []. The setup brief andagent/json.mddescribe it, and
signalspublishesdependency_dirs.
Changed
- A setup run by the developer's agent asks them nothing, start to end.
The brief has the agent decide every question pando's rules leave
open — the apps to run (all of them), the runtime linedoctor
lists, a worktree's.envseeded from the example when there is no
other, the main checkout's branch as the base when a check fails on
it — and end with a report of what it set, why, and how to change it.
Saving the run instructions in the agent's memory is offered in that
report and done only when the developer says to.
Install pando-cli 0.8.3
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.8.3/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.8.3
| 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/pando0.8.2 — 2026-10-05
Release Notes
Added
pando update: updates pando to the latest release the way it was
installed —brew upgradefor Homebrew's,cargo installat the
release's tag for cargo's, and the install script, into the directory
the binary is in and with no change to shell files, for any other. A
build made in a checkout is updated there, so pando says how and runs
nothing.--checksays whether a newer release is out and what would
install it.
Install pando-cli 0.8.2
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.8.2/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.8.2
| 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