PandaCode 0.3.26

Current GLM Coding Plan models

Fixes

• The GLM Coding Plan picker lists the models Z.AI actually serves. The new default is GLM-5.3, alongside GLM-5.3-Flash, 1M-context versions of both, and GLM-5-Turbo. The old IDs (glm-4.7, glm-5.1) were being quietly routed to newer models on Z.AI's side. Claude Code's fast background model is now GLM-5.3-Flash. Thanks @DreDay4u (#86).

Known limitations

• Tasks that saved an old GLM model ID keep it. Z.AI routes it to a current model. Pick GLM-5.3 in the model picker to make the choice explicit.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• macOS (Intel): open PandaCode-macOS-x64.dmg and drag PandaCode to Applications (same Open Anyway step if macOS cannot verify the app).
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Windows arm64: run PandaCode-Windows-arm64-setup.exe (same SmartScreen step).
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.25

Windows on ARM and app-wide lead guidance

New

• Windows on ARM. A native PandaCode-Windows-arm64-setup.exe for Snapdragon and other ARM64 Windows PCs, with automatic updates. npx pandacode installs it.
• One lead guidance for every team. Settings → Agent teams has a Lead guidance field that applies to every team. A team's own guidance still replaces it for that team, and resetting a team's guidance returns it to the app-wide one. Thanks @ktappdev (#79).

Fixes

• The agent team editor is readable again. The Filter models field is full height, and model names stay visible beside their effort dropdowns. Thanks @ktappdev (#84).

Known limitations

• The Windows ARM64 build is new and hasn't been tried on a real ARM64 PC yet.
• After app-wide lead guidance is set, an older PandaCode version can't read the saved team library. Clear the guidance before downgrading.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• macOS (Intel): open PandaCode-macOS-x64.dmg and drag PandaCode to Applications (same Open Anyway step if macOS cannot verify the app).
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Windows arm64: run PandaCode-Windows-arm64-setup.exe (same SmartScreen step).
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.24

Chats, connections, a design canvas and a skills library

New

• Chats without a project. New chat starts a conversation that isn't tied to a codebase. Each chat gets its own folder under ~/PandaCode Chats, chats are listed in their own Chats section, and project-only controls are hidden. Move to project… moves a chat into a project before it gets going.
• Named connections for each agent. Add "Claude Work" and "Claude Personal", or two Pi profiles. Each connection has its own executable, arguments, environment and config folder, and secret values are kept in the system keychain. Choose a connection per task in the model picker, and tasks keep theirs.
• Design canvas. Agents can create HTML artboards. You see them in the inspector's Design tab, pan and zoom around them, click an element to comment on it, and send the comments back to the agent. Artboards are files in .pandacode/design, so they show up in diffs and reviews.
• Skills & rules library. Import a skill or rule from a folder or a GitHub repository, then turn it on for each agent, either globally or for a project. The library shows which agent has what, spots edited or unmanaged copies, and scans for secrets or approval-bypass instructions before anything is turned on. It never overwrites files it didn't write.
• Jujutsu. Jujutsu (jj) repositories get their own Changes panel: change ID, description, bookmarks, changed files, diffs, Describe, New, Commit and the log. Repositories that also use Git show a jj chip.
• Capabilities & cache. Settings → Tools & add-ons lists each agent's commands, MCP servers, hooks and skills side by side, without exposing secrets. It also shows how PandaCode's instructions are cached for each agent, with the cache tokens the agent reported.
• Workflow recipes. Save multi-step routines as recipes, such as review, check, summarise and wait for approval. A dry run shows what each agent can do natively and what needs a fallback. Running a recipe queues its steps as ordinary messages. Open recipes from the + menu.
• GitHub Copilot CLI as an agent. Thanks @238SAMIxD (#73).
• Workspace search. The inspector has an activity bar and a Search tab with find-in-files results. Thanks @SakithaSamarathunga33 (#72).
• Project checks after turns (off by default). When an agent finishes cleanly, PandaCode runs the project's own test or check command. If it fails, one editable fix message is queued; it never loops. Thanks @matkarimov099 (#68).
• Code search for agents. If codedb is installed, agents get a fast, read-only code search tool, with codedb's telemetry and background daemon turned off. Thanks @matkarimov099 (#65).
• New task from a project heading. Hover over or focus a project in the sidebar to start a task there. Thanks @jojomensah89 (#76).
• Intel Macs. A native PandaCode-macOS-x64.dmg is published with automatic updates, and npx pandacode installs it.

GitHub view

• Keyboard navigation works everywhere. The arrow keys move through workflow runs as well as pull requests and issues, and Enter opens the focused row.
• Run details go deeper. Expanding a run shows each job's steps with durations, the job's summary and earlier attempts.
• Check workflow files asks an agent to find invalid YAML, unknown runner labels and broken uses: references.

Fixes

• Node from fnm, nvm, mise, asdf or nvm-windows is found, so agents installed with npm under a version manager work when PandaCode starts from the Dock.
• Pi installed with the pi.dev installer works on Windows.
• The project picker no longer closes as it opens right after a new task is created.
• A board task you open while PandaCode is still starting stays open.

Known limitations

• Jujutsu support, codedb search and Copilot have been tested against recorded output only, not live installs.
• The Intel macOS build is new and hasn't been tried on a real Intel Mac yet.
• The design canvas runs no scripts inside artboards, so interactive prototypes appear static.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• macOS (Intel): open PandaCode-macOS-x64.dmg and drag PandaCode to Applications (same Open Anyway step if macOS cannot verify the app).
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.23

Readable agent traces

Tool activity

• Tool calls read as sentences. Instead of raw tool names, each call says what it did: "Ran rg -n createSearchIndex src", "Read search-index.ts", "Searched src for toLowerCase", "Edited search-index.ts +4 −3", "Fetched developer.mozilla.org", "Updated the plan · 3 steps". MCP tools name their server and tool.
• Groups summarise themselves. A group of calls is one line, such as "Ran 1 command and 2 searches, read 1 file and edited 1 file", with an icon for each kind. While it runs it reads "Reading 2 files…". Failed calls are counted separately and marked in red.
• Expanded rows show the work. Opening a row shows command output, file contents, matched files or a red and green diff. The raw input and output are still there, one click further in.
• Everywhere you see tools. The same traces appear in conversations, the board, the quick launcher, subagents and team workers.

Fixes

• Raw output stays open while a subagent streams. Updating a subagent's tool row no longer closes the raw output you were reading.

Known limitations

• The new traces have been tested in Chrome but not yet in WebKit, the engine the macOS app uses.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.22

Stay signed in, pick models that exist

Remote access

• PandaCode Connect stays signed in across updates. Updating no longer asks you to sign in again. If 0.3.20 or 0.3.21 signed you out, 0.3.22 picks up your earlier sign-in by itself, as the same computer, so the computers you trusted stay trusted. A brief Keychain hiccup right after an update is retried quietly instead of signing you out, and your sign-in renews itself before it expires.
• The model picker shows what the other computer has. For a task that runs on another computer, the picker lists only the providers and models installed there. If your current model isn't on the computer you pick, PandaCode switches to one that is and tells you; picking This computer again brings your choice back.

Known limitations

• If the earlier sign-in can't be found (for example it was removed from Keychain), sign in once more in Settings → Remote access.
• Remote access is covered by automated tests; it has not been tried between two real computers yet.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.21

Oh My Pi, Command Code and a better GitHub view

New agents

• Command Code. Run Command Code as an agent through its ACP server. Its models, effort levels and slash commands appear in PandaCode, and Standard, Accept edits, Plan and Full access use Command Code's own permission modes. You can save an API key in the system keychain, or sign in with command-code login. Thanks @ktappdev (#56).
• Oh My Pi (omp). Run omp, the Pi fork, as an agent. It uses your existing omp login and setup.

Teams

• Lead guidance. Team setup can carry your own rules for the team lead, for example "only coordinate, never edit files". They're added after the built-in rules. Reset to default clears them. Thanks @ktappdev (#61).
• Effort for each role. In Settings → Agent teams you can set the lead's effort separately from the workers'. For example, the lead can run at High while the workers run at Medium.

GitHub view

• Actions make sense next to pull requests. Each run shows its event, its pull request, how many attempts it took and how long it ran. You can filter runs by event or pull request, or keep only the latest run per pull request. Each pull request has a Runs link to its runs.
• Run details. Expanding a run shows its jobs with their durations, and its artifacts with their sizes.
• Workflows that never started. A run GitHub couldn't start, for example because of an invalid workflow file or a missing runner, now reads "Didn't start". Its Fix action asks the agent to check the workflow file.
• Typing is no longer erased. Text you type in the GitHub view now stays when the view refreshes.

Everywhere else

• Remove a project. Settings → General → Projects lists your projects and can remove one, including one whose folder was deleted. The project's tasks are removed from PandaCode; the folder stays on disk.
• Drag the window by its header again on macOS.
• Links open in your browser. Links in Markdown, provider cards and the quick launcher now open in your default browser. Thanks @jojomensah89 (#40).
• File icons. The Files tab, the @ menu and changed-file lists show Material Icon Theme icons. They load the first time they're needed, not at startup. Thanks @SakithaSamarathunga33 (#49).
• Task timers and defaults. Working tasks show how long they've been running. Settings has a default model for new tasks and an Expand tool activity option for past turns; a running turn's activity always stays open. Thanks @ExcuseMeBro (#37).
• Linux arm64. A native PandaCode-Linux-aarch64.AppImage is published with automatic updates, and npx pandacode installs it.
• Android emulators on Windows. The Simulators tab lists Android devices on Windows. Without an SDK, it explains how to install one.

Fixes

• Agents work again from the Linux AppImage. The AppImage's own library and Python paths no longer reach agents, terminals or git. These had broken /usr/bin/env ("version LIBSYSTEMD_254' not found"), curlandpython3` in agent shells.
• Grok Build is found in ~/.grok/bin, where its official installer puts it.
• A warm Claude agent that isn't reused is now logged with the reason, to help track down slow follow-up turns.

Known limitations

• The Linux arm64 build and the Windows Android support have not been tested on real machines yet.
• Oh My Pi has been tested against recorded messages only, not a live install. Run omp with Bun, as its installer sets up.
• Command Code can't be steered mid-turn: messages you send during a turn are queued.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Linux arm64: chmod +x PandaCode-Linux-aarch64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.20

Run a task on another computer

Remote access

• Choose the computer beside Local and Worktree. Once you're signed in to PandaCode Connect, the bar above the prompt box lists This computer and your trusted, online computers. Pick one and send: the task runs there, and everything else works exactly like a local task: the same sidebar row, transcript, streaming, queue, Stop, approvals, model and permissions. The separate Computers section and remote view are gone.
• The other computer gets the project for you. It opens the same GitHub repository if it already has it, or clones it into ~/PandaCode, then uses the same branch. With Worktree it works in a fresh worktree, and it never switches a checkout that has uncommitted changes or a running agent.
• You're warned when GitHub is behind. If this computer has unpushed commits, uncommitted changes or an unpushed branch, PandaCode tells you the other computer will start from GitHub's version and asks before continuing.
• Fast and light. The other computer pushes its agent's output about ten times a second at most, and messages are copied once per run, so nothing polls.

Fixes

• Fixed "Could not read this computer's PandaCode Connect key from Keychain (-25293)". It happened when two PandaCode builds on one Mac shared a keychain entry. Each install now has its own entry; sign in to remote access once more after updating.

Known limitations

• Images and browser captures can't be attached to a task that runs on another computer yet.
• Changes, diffs and commits for a remote task stay on the computer that runs it.
• Remote access has been tested with automated tests only, not yet between two real computers.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.19

Control your other computers

Remote access

• PandaCode Connect lets one PandaCode drive another. Sign in with GitHub in Settings → Remote access on each computer. Turn on Allow remote control of this computer on the one you want to drive, and mark the computers Trusted on each other after comparing their fingerprints. Your other computers then appear under Computers in the sidebar. From there you can read their tasks as they stream, send messages, start new tasks, stop runs and answer approvals.
• It's off until you sign in. Nothing is sent anywhere before that. After sign-in, PandaCode keeps one connection to the PandaCode relay, which runs on Cloudflare. Messages between your computers are encrypted end to end (X25519 and XChaCha20-Poly1305), so the relay forwards only ciphertext and stores no task content. Remote prompts follow the approval settings of the computer they run on.
• It's free, with up to 10 computers per account.

Known limitations

• Remote access was tested with automated tests only; it has not been tried between two real computers yet.
• A computer must stay awake and online to be controlled. One that sleeps shows as offline within about 75 seconds.
• Very long transcripts load in pages, and a single message over 120 KB is shortened in the remote view.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.18

Install with one command

Installing

• npx pandacode installs PandaCode. It downloads the latest release from GitHub, checks it against PandaCode's update signing key before installing anything, and installs the right build: macOS Apple silicon into Applications, Windows x64 with a silent install, Linux x64 as an AppImage in ~/.local/bin with a menu entry. npx pandacode --dry-run downloads and verifies without installing.

macOS

• PandaCode signs itself on your Mac. The app is signed with a certificate created once on your machine and kept in its own keychain, without any prompt. It happens on install, at startup and after every automatic update, so keychain access and privacy permissions now survive updates instead of being asked for again.

Known limitations

• The first local signing changes the app's identity once, so macOS may ask one more time for keychain access to secrets PandaCode saved before.
• Local signing does not satisfy Gatekeeper; installs through npx avoid the first-launch warning because the download is not quarantined.
• The Windows and Linux npx installs have not been tried on real machines yet.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.
• Any of the above, from a terminal: npx pandacode downloads, verifies and installs the right build (macOS: signed locally automatically).

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.

PandaCode 0.3.17

A smoother, more reliable iPhone Duo

Simulators

• Folding no longer freezes PandaCode. In 0.3.16 the loading spinner on the Duo's display redrew the whole screen image on every frame and could stall the window until the new screen arrived. It now costs almost nothing, and the 3D view stops drawing when nothing moves.
• Folds happen first and always land. The 3D Duo folds the moment you click; the simulator follows in the background. Clicking several poses quickly ends on the last one, and only that one is sent. Closing is reliable again: the hinge sweeps for 0.2 s instead of jumping, waits for the previous switch to settle, and recovers by way of a half-open position if the simulator misses a fold. Ten open/close cycles in a row each finished in about 1.2 s.
• Agents tap the right thing on the inner display. With the Duo open, finding a button by its label returned the cover display's position, so taps landed in the wrong place. PandaCode now reads element positions on the inner display from the simulator itself, and agents can find app content there that was missing before.

Known limitations

• Describing the inner display takes 2–4 seconds longer than the cover display.
• If the simulator's SpringBoard gets stuck mid-fold, folds stop switching displays until the simulator restarts.
• iPhone Duo needs Xcode 27.1 or later on macOS.

Installing

• macOS (Apple silicon): open PandaCode-macOS-arm64.dmg and drag PandaCode to Applications. If macOS says it cannot verify the app, open System Settings > Privacy & Security and choose Open Anyway.
• Windows x64: run PandaCode-Windows-x64-setup.exe. If SmartScreen warns about an unknown publisher, choose More info > Run anyway.
• Linux x64: chmod +x PandaCode-Linux-x86_64.AppImage and run it.

Each file has a .sha256 checksum beside it. Installed copies update themselves from this page. Build from source: see CONTRIBUTING.md.