From the DSH plugin ecosystem to pi: are we missing an official Web UI base? | 从 DSH 插件生态看 pi：我们是不是缺一个官方 Web UI 底座？

[buhuikongpan]

中文

从 DSH 插件生态看 pi：我们是不是缺一个官方 Web UI 底座？

DSH（DeepSeek Harness）正式发布的时候，我确实被震撼到了。"一切皆插件"（Everything is a Plugin）这套理念，和我们 pi 的"极简内核 + 通过扩展/技能自由扩展"思路非常相似。更让我高兴的是，中国社区的朋友们很快就投入到了 dsh 插件的开发里，社区一下子热闹起来。

不过我注意到一个很有意思的现象：DSH 的插件贡献者里，有相当大一批人都在写 UI 向的插件——聊天界面、工作区面板、终端嵌入、状态栏之类的。反观 pi 这边的插件社区，整体更偏向功能向（工具、命令、事件处理、SDK 集成这些）。

我个人的猜测是，这个差异可能源于两点：

1. 个人偏好：大家各有所爱，这很正常；
2. 更关键的可能是 DSH 第一版就自带了一个官方 Web UI，等于官方给了一个统一的、可创作的 UI 底座，大家在这个底座上做 UI 扩展的门槛很低，也容易互相参考、组合。

而 pi 是跑在终端里的，一直没有官方 Web UI 作为那个"底座"。扩展虽然也能渲染 UI（比如自定义 widget、状态栏、覆盖层），但没有一个统一的可视化画布，UI 向开发各自为战，门槛和组合成本都更高——这也许就是 pi 社区 UI 向插件相对偏少的原因之一。

所以我很好奇一件事：pi 未来有计划做官方 Web UI 版本吗？

如果做的话，我个人很期待，因为：

• 它能成为像 dsh webui 那样的统一 UI 底座，降低 UI 插件开发门槛；
• 多端访问（浏览器、远程、移动端）会更方便；
• 对"功能向 + UI 向"两拨贡献者来说，都是一个更好的舞台。

想听听大家怎么看，也欢迎抱走 pi 团队的官方思路。

---

English

Pi missing an official Web UI base? Observations from the DSH plugin ecosystem

The release of DSH (DeepSeek Harness) genuinely blew me away. Its "Everything is a Plugin" philosophy feels very close to pi's own approach — a minimal core that you extend freely via extensions, skills, prompt templates, and themes. I was also really glad to see friends from the Chinese community jump straight into DSH plugin development. The ecosystem took off quickly.

But I've noticed an interesting pattern: a large share of DSH plugin contributors are building UI-focused plugins — chat interfaces, workspace panels, embedded terminals, status bars, and so on. Meanwhile, pi's plugin community leans much more toward functional plugins (tools, commands, event handlers, SDK integrations).

My guess is this comes down to two things:

1. Personal preference — everyone has their own taste, which is totally fine;
2. More importantly, DSH shipped an official Web UI from day one. That's essentially a unified, ready-made UI canvas that lowers the barrier for making UI extensions — people can build on it, reference each other, and compose freely.

Pi, by contrast, runs in the terminal and has never had an official Web UI as that "base." Extensions can render UI (custom widgets, status lines, overlays), but there's no unified visual canvas, so UI-oriented development is more scattered — with a higher barrier and higher cost to combine. That's probably one reason pi's community has relatively fewer UI-driven plugins.

So here's my question: does pi have any plans for an official Web UI?

If so, I'd personally be excited, because it would:

• Give pi a unified UI base like DSH's web UI, lowering the barrier for UI plugin development;
• Make multi-device access (browser, remote, mobile) much more convenient;
• Provide a bigger stage for both "functional-oriented" and "UI-oriented" contributors.

Curious to hear everyone's thoughts — and any roadmap hints from the pi team would be great too.