智能体
dev.to ·
@vastsa
PI-Desktop:面向 AI 编码 Agent 的本地优先工作台
作者介绍 PI-Desktop,一个面向 AI 编码 Agent 的本地优先桌面工作台,可在 macOS、Windows 和 Linux 运行,当前版本 v0.15.1,仓库约有 4.6k GitHub stars 与 390 forks。主要用途包括:跨重启保留项目上下文与会话历史;自由切换模型与供应商;Plan 与 Goal 模式,从模糊需求生成可编辑计划再执行;权限控制与 diff 审查,将破坏性操作置于审批之后;通过插件与 MCP 扩展工具集成。
AI推荐理由 介绍本地优先的 AI 编码 Agent 工作台 PI-Desktop v0.15.1,具备持久项目/会话、模型切换、权限控制与 diff 审查、插件与 MCP 等能力,对开发者工具选型有参考价值;但为作者自述,星标与 fork 数不能证明工具可靠性,缺少独立评测。
60
正文
I wanted a place where an AI coding session could keep its context instead of starting from a blank terminal every time.
That is the idea behind PI-Desktop: a local-first desktop workspace for AI coding agents. It brings persistent projects, sessions, model switching, permissions, and multi-agent workflows into one app that runs on macOS, Windows, and Linux.
The current release is v0.15.1. The repository has roughly 4.6k GitHub stars and 390 forks.
What I use it for
Persistent projects and sessions — project context and conversation history stay available across restarts.
Model freedom — switch providers and models without rebuilding the whole workflow around one vendor.
Plan and Goal modes — move from a vague request to an editable plan, then execute it with visible progress.
Permission controls and diff review — keep destructive actions behind approval and review file changes before accepting them.
Plugins and MCP — extend the workspace with tools and integrations instead of putting every workflow into the core app.
Multi-agent workflows — delegate independent work to subagents and keep the main session focused.
Why a desktop workspace?
Terminal coding agents are powerful, but long-running work quickly turns into a collection of terminals, scrollback, copied prompts, and half-remembered decisions. A desktop workspace gives those sessions a home.
PI-Desktop is built with Electron, a Rust host core, and the pi agent harness. The goal is not to hide the agent behind a simplified chat box. It is to make the surrounding work easier to inspect: what the agent changed, which tools it used, what still needs approval, and where another agent can help.
The local-first approach also matters to me. Your projects and sessions should remain usable without handing the whole workflow to a hosted dashboard.
Links
GitHub repository
Documentation
Latest release
If you build with AI coding agents, I would especially like feedback on the session model, permissions, and multi-agent workflows.