PandaCode

A small, native desktop workspace for coding agents. PandaCode runs the coding CLIs you already use — Claude Code, Codex, Kimi Code, OpenCode, GLM Coding Plan and Xiaomi MiMo (through Claude Code), Antigravity and xAI's Grok Build (through ACP) Pi (through its RPC mode) and DeepSeek (through ACP) — side by side, with your projects, Git, a terminal and a browser in one window.

PandaCode is free and open source under the PandaCode License, the MIT License with one addition: forks that are used commercially or released publicly must say "This is a fork of PandaCode" and link to this repository. There is no account, no license key and no telemetry.

Built with Tauri 2, Rust, SQLite and plain TypeScript. It uses the operating system's webview: no bundled Chromium, resident Node server, React runtime or embedded editor engine.

Download: macOS (Apple silicon) · Windows x64 · Linux x64 · All releases

• Every harness in one place. Pick the harness, model and reasoning effort per task; switch between them from the composer. See providers.
• Tasks and a task board. Parallel tasks across projects, a Pending → In progress → Review → Completed board, message queueing and steering while an agent runs.
• Agent teams. An architect and up to three workers, mixing harnesses and models, or named team profiles. Each spawned worker is one line in the turn that started it; click it to open the worker.
• Bots. Put an agent behind Telegram, Slack, Discord, WhatsApp or a local web chat; each conversation is an ordinary task. The sidebar's Bots view lists every bot with its latest message. See bots.
• Local VMs and cloud sandboxes. Headless macOS/Linux VMs on Apple silicon (Tart), and Daytona, Cloudflare and AWS sandboxes that agents can drive.
• Simulators. iOS Simulator and Android emulator tools for agents.
• Deploys. Start a deploy task for Vercel, Cloudflare, Railway, AWS or Google Cloud from the header, with approval-gated CLI runs (AWS and Google Cloud use your installed CLI and its login).
• GitHub view. Your repositories with their threads, pull requests and issues; review, fix checks, merge or solve an issue in one click. Each opens as a linked thread beside the GitHub view, where you can keep chatting. See GitHub.
• Git and worktrees. Diffs, staging, commits, per-task worktrees with a one-click local Merge into main, branch switching from the branch chip, and optional GitHub issues and pull requests through gh, including merging a task's linked pull request.
• Approvals at hand. Requests wait in a slim bar above the prompt, one line each, grouped with Approve all when there are several.
• Find in thread. ⌘/Ctrl F searches your messages and the agent's, with every match highlighted.
• Review every turn. Saved turn changes with unified/split diffs, an embedded browser, and file previews.
• Token saver. Per-task response-style packs that cut output tokens.
• Quick overlay. A global shortcut (default ⌘/Ctrl + Shift + Space) opens a launcher for new and running tasks from anywhere.
• Agent usage. Account limits and cost estimates for each installed harness (agent usage), and one-click CLI updates (agent updates).
• Attachments. Images, PDFs, documents, folders and a built-in mockup sketcher (attachments).

A board for everything in flight. Tasks from every project move from Pending to Review, each with its harness, model and linked issue.

Live replies. Responses stream in as Markdown, with tool activity folded above.

Any harness, any model. Switch per task, with context size and reasoning effort.

Agent teams. An architect plans the work, runs workers in parallel across harnesses, and reviews what they bring back.

Your app beside the chat. The iOS Simulator and Android emulator run in the inspector on a lifelike device, so you can tap through what an agent just built.

Bots that keep working. A bot's conversation is an ordinary task thread, with the same streaming, composer and model picker; reach it from Telegram, Slack, Discord, WhatsApp or a browser too.

Review every turn. Each turn saves its changes, with unified and split diffs.

Bot settings. Memory, schedules, channels and rules, in one place.

_{Screenshots come from the browser preview with sample data. Regenerate them with npm run screenshots (see scripts/screenshots).}

• No telemetry, no analytics, no accounts. PandaCode does not phone home.
• Your code stays on your machine. Projects, conversations and settings are stored locally in SQLite. Prompts go only to the coding CLI or service you pick, under that provider's own terms.
• It only talks to services you choose. Provider keys (GLM, MiMo, DeepSeek, cloud sandboxes, bot channels) live in the system keychain and are sent only to that provider.

A few automatic checks send no personal data — just plain requests for public information:

Download the latest build from GitHub Releases:

Or from a terminal: npx pandacode downloads the latest build, verifies its signature and installs it (on macOS it is signed locally for you, so no Gatekeeper prompt). npx pandacode --dry-run only downloads and verifies.

Release builds are not code-signed, so your OS will warn the first time:

• macOS: if macOS says it cannot verify PandaCode, open System Settings → Privacy & Security and click Open Anyway.
• Windows: if SmartScreen appears, click More info → Run anyway.
• Linux: chmod +x PandaCode-Linux-x86_64.AppImage, then run it. Some distributions need FUSE 2 (libfuse2), or set APPIMAGE_EXTRACT_AND_RUN=1.

Each file has a .sha256 checksum beside it. Once installed, PandaCode updates itself: it checks the latest release, downloads a newer version in the background, verifies its signature, and restarts to install it when no agent is working and you've stepped away (or when you click Restart to update). Turn this off in Settings → About. See platform support for details.

Then install Git and at least one coding CLI and sign in with its normal login. PandaCode does not include provider plans or usage.

Pi installs with npm i -g @earendil-works/pi-coding-agent; sign in through Pi's own CLI. PandaCode drives it over Pi's RPC mode and gives it PandaCode's app tools through a local loopback bridge extension. Pi has no approval system of its own, so PandaCode's extension enforces the permission modes; the integrated console needs Full access.

DeepSeek installs with npm i -g @deepseek-ai/dsh; PandaCode launches dsh --profile acp. An API key is optional (Settings → Providers, or DEEPSEEK_API_KEY); dsh can use its own stored credentials. Usage limits are not shown in PandaCode; check platform.deepseek.com.

You need Node.js 22, stable Rust, and the Tauri prerequisites for your OS.

git clone https://github.com/aicodeking/pandacode.git
cd pandacode
npm ci
npm run desktop        # same as: npm run tauri dev

npm run dev serves only the frontend. In a regular browser it runs a labeled, device-local sample workspace for UI work; files, Git and terminals are simulated there. npm run tauri build makes a local installer, and npm run release:build builds the release asset for your OS (see releasing).

The website lives in website/: npm run site:dev and npm run site:build.

Open a project folder, then click New task or press ⌘/Ctrl N. A centered "What should we build in …?" page opens in the last active project with the message box focused. Choose the harness and model from the searchable picker in the message box; new tasks remember your last choice. The + button attaches images, documents, folders, project files or a mockup. Open Changes to inspect and stage diffs, or the terminal to run shell commands. Conversations and provider session IDs persist across restarts; agents start only for active turns.

In Files, click an HTML, SVG, image or PDF to open it in the sidebar browser. Filenames mentioned in responses become clickable and resolve against the task's own project or worktree.

The bar above the prompt shows the project, checkout and branch. Its branch chip is the one place for worktrees: an unstarted task moves into a new worktree in place, a started one spawns a sibling task, and archiving a clean worktree task offers to remove its checkout and merged branch.

Choose Board in the header to manage tasks by status. Choose Team in the composer for an automatic team, or set up an architect and workers. Each turn's tool calls sit inside a compact Worked for … row; final answers and errors stay visible, and approval requests wait in the bar above the prompt.

The branch chip also switches the project checkout to main or another local branch, and in a worktree task offers Merge into main: it merges the worktree's committed work locally, refuses uncommitted changes or conflicts without touching anything, then offers to remove the worktree.

Standard permissions keep each provider's native checks. Claude's Accept edits allows its editing tools; Codex uses its workspace sandbox with on-request approvals. Full access enables the harness's broadest mode. See provider details.

Type / at the start of a message for the harness's commands and skills (slash commands).

Keyboard shortcuts: ⌘/Ctrl N new task, ⌘/Ctrl K command palette, ⌘/Ctrl J terminal, ⌘/Ctrl B sidebar, ⌘/Ctrl , settings, ⌘/Ctrl F find in thread (⌘/Ctrl G next match), Enter send (queues while an agent runs), ⌘/Ctrl Enter steer, Shift Enter newline, ⌘/Ctrl +/−/0 interface size (the whole interface scales, not just text).

On macOS, if folder access is denied, use Browse to select the folder, or allow PandaCode under System Settings → Privacy & Security → Files & Folders.

PandaCode includes 21 anime scenery wallpapers, a different morning, afternoon and night scene for each weekday. Settings → Daily wallpapers turns them off. You can also import VS Code color themes.

The optional Jev add-on adds work review, project-rule checks and app testing in isolated Chrome profiles. It is off by default and PandaCode works fully without it.

No background directory polling or recursive file watchers. Agents exit after each turn and resume by provider session ID. After a Claude Code turn, the next turn's process starts in the background so a follow-up skips the CLI's startup; at most two wait at a time, each for up to 10 minutes. PandaCode's fixed instructions go to Claude-family harnesses once as a cached system prompt rather than in every message. The interface has no transitions: everything appears at once, and a thread you return to is drawn in a single frame. Terminal and Markdown code load only when needed. Terminal history, provider frames, files, diffs and streamed text all have explicit limits; only the current 100-message page of a conversation is loaded. Resource usage reports native core RSS, active agents, terminals and database size (core RSS excludes the system webview and provider processes).

npx tsc --noEmit           # typecheck
npm run build && npm test  # unit tests (some read dist/)
npm run test:release       # release script tests
npm run test:rust          # cargo test
npx playwright test        # browser suite (Chrome)
npx playwright test -c playwright.webkit.config.ts   # WebKit

Ordinary tests make no paid model calls. Opt-in live tests are #[ignore]d; see providers.

Contributions are welcome. Read CONTRIBUTING.md for setup and the pull request process, and AGENTS.md for code conventions. Please follow the Code of Conduct, and report security issues privately as described in SECURITY.md. Bugs and ideas go in GitHub issues.

Architecture notes: design, native IPC, research. Provider protocols live in src-tauri/src/providers.rs behind one normalized event interface; ACP harnesses share acp.rs.

Data lives in Tauri's per-user application data directory (on macOS, ~/Library/Application Support/ai.pandacode.desktop/) in kingcode.sqlite3; the database keeps its legacy internal name. Project source stays in the folders you open, and removing a project from the app never deletes its files.

PandaCode License (MIT with an attribution requirement for forks) © 2026 PandaCode contributors. Provider names and logos belong to their owners and do not imply endorsement (brand assets).