[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f3vi6o9d11aiix":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"aicodeking\u002Fpandacode",9,"PandaCode: a calm desktop workspace for coding agents","Rust",625,122,90,7,[],"A desktop app that runs several coding-agent CLIs side by side, with tasks, Git, terminal and browser in one window.","PandaCode is a native desktop shell for coding-agent CLIs you already use. It is worth a look if you keep several agents running on the same projects and lose track of them across terminal tabs; skip it if you need only one harness or want your editor to drive the agents.\n\n## The problem\n\nWorking with a coding agent usually means a terminal per session, an editor for diffs, a browser for docs and a notes file for what is in flight. When two agents work on different branches, you become the coordinator: copy the task into a new shell, remember its folder, then hunt for its output. PandaCode keeps the project folder as the unit and turns each assignment into a task with a harness and model attached, so parallel runs across projects appear on one board. The message box steers a running agent, and you get a single place to see what is pending, in progress, in review or done.\n\n## What's different\n\nPandaCode ships no model or agent loop. It wraps existing CLIs — Claude Code, Codex, Kimi Code, OpenCode, GitHub Copilot CLI, Cline, Kilo Code, Pi and others — through their own protocols, and lets you choose harness, model and reasoning effort per task. The quality and quirks you know from each CLI carry over, along with your provider login. The interface is deliberately plain: no bundled Chromium, no resident Node server, no React runtime, no UI transitions; the stated goal is a calm workspace and a small footprint.\n\nThe ambitious part is coordination. An architect agent can spawn up to three workers, mixing harnesses and models, and each worker shows as a line in the turn that started it. Tasks can be exposed as Telegram, Slack, Discord or WhatsApp bots, where each conversation is an ordinary task. Runs can go to local Tart VMs on Apple silicon or to cloud sandboxes in your own account, with PandaCode installing the harness and copying your login there. That breadth is the trade-off: a young coordinator is handling provider credentials on remote machines, and each [supported harness](https:\u002F\u002Fgithub.com\u002Faicodeking\u002Fpandacode\u002Fblob\u002Fmain\u002Fdocs\u002Fproviders.md) brings its own protocol edges.\n\n## Who should try it\n\nGood fit: a developer who already pays for one or more coding CLIs, runs several on the same repository, and wants a board, diffs, a terminal and a browser in one window instead of editor plus tmux plus notes. Someone who wants agents reachable from a chat channel, or wants to try [cloud sandboxes](https:\u002F\u002Fgithub.com\u002Faicodeking\u002Fpandacode\u002Fblob\u002Fmain\u002Fdocs\u002Fbots.md) without writing the plumbing, has a concrete reason to install. Poor fit: anyone working mainly inside a full IDE who is happy with its agent panel, or who needs a single harness, gets more from the CLI directly. The release path is signed installers for macOS, Windows and Linux plus `npx pandacode`, so building from source is not required.\n\n## Requirements and limitations\n\nSupported platforms: macOS 12+, Windows 10 1809+\u002F11 (x64 and arm64), and Ubuntu 22.04+ or 24.04+ on arm64 with X11 or XWayland. On macOS provider keys sit in a plain `secrets.json` readable only by your user rather than the Keychain, which avoids update password prompts but makes file permissions the protection; Linux uses the Secret Service and Windows Credential Manager. PandaCode sends no telemetry but does make scheduled plain requests for CLI versions, model prices and its own updates, which can be turned off in Settings.\n\nBuilding from source needs Node.js 22, stable Rust and the Tauri prerequisites; `npm run dev` alone serves a simulated workspace with fake files, Git and terminals. Local VMs are limited to Apple silicon via Tart, and cloud runs need your own account with a listed provider. Data lives in a local SQLite file, and removing a project does not delete its files. The [license](https:\u002F\u002Fgithub.com\u002Faicodeking\u002Fpandacode\u002Fblob\u002Fmain\u002FLICENSE) is MIT plus a fork-attribution clause, which matters if you redistribute a modified build.\n\n## HotRepo's take\n\nHotRepo has tracked PandaCode since 2026-10-24. The only recorded signal is #9 on the NEW-REPOSITORY board (新项目榜, not the overall Trending board) for Rust on 2026-10-25, with 625 total stars at that observation. The repository was created on 2026-10-18, so this is a week-old project with one dated board sighting; persistence cannot yet be judged, and the star count is a snapshot, not a growth rate. Before relying on it, check the provider notes against the CLIs you actually use.",{"slug":19,"name":20},"developer-tools","Developer Tools",[],"NOASSERTION",null,"2026-10-25T02:46:29Z",[],1792906270]