Thank you for using PI-Desktop — we read every report

[vastsa]

Thank you

Thank you for using PI-Desktop, and thank you for every bug report, feature request, pull request, and kind word.

We read every issue. We consider each one carefully, and we will work through them. Your feedback is how this project gets better, so please keep sending it.

Please be patient with the queue

The issue list is large right now, so replies and fixes may take longer than we would like. That delay is not a lack of attention. We have not forgotten your report, and we will get to it.

Thank you for understanding, and thank you for helping us build PI-Desktop.

How to report

Please use the issue forms and search existing issues first:

• Bug report
• Feature request

[Akshayxkill]

What is the process of getting my plugin on the marketplace and also i have made some huge changes to the core pi-desktop i really loved the workflow of superpowers aka skills codex using and wrote them for scratch for pi-desktop.
The link to the fork is https://github.com/alphalaughs2024-netizen/PI-Desktop-fork
check it out! also added a custom theme

[Tioit-Wang]

Thanks for the kind words and for sharing this — building a workflow/skills system plus a full theme from scratch is a lot of work, and we appreciate the effort.

Getting a plugin into the marketplace

The catalog the desktop reads lives in vastsa/pi-desktop-plugins, and the end-to-end steps are in its CONTRIBUTING.md. In short:

1. Fork that repo and start from plugins/demo.workspace-summary.
2. Fill in manifest.json and main.js, requesting only the permissions you actually need.
3. python3 scripts/pack_plugin.py plugins/<id>, then python3 scripts/rebuild_catalog.py.
4. python3 scripts/security_audit.py --check-packages must pass with zero blockers.
5. Open a PR.

After it merges, the raw catalog.json updates and your plugin shows up in Plugins → Marketplace (click "Refresh from repo"). Packages must be self-contained — no host-side npm install, 50 MB limit — and high-risk capabilities get an extra review with two maintainer approvals. The publishing console is not live yet, so pack → rebuild catalog → PR is the current path. Please also add i18n entries for en and zh-CN, since the marketplace surfaces them.

On themes

The built-in set is intentionally just light and dark. Everything beyond that is meant to arrive as a plugin, and themes are already a first-class contribution: declare contributes.themes with a .css file and the ui.theme permission, pick a light or dark base, and the host sanitizes the CSS (it cannot script) and offers it in the theme picker. pi.parchment in the marketplace is a working reference for the shape.

So a theme like Twilight Mountains is very welcome — just as a plugin rather than as a core change. If the theme contribution API cannot express something your visual system needs, please open a feature request for the missing capability. That is exactly the kind of feedback we want to have, and it is much more useful to us than a fork we cannot merge.

On Nexus

To be honest, we do not yet have a clear picture of what Nexus adds. The README lists quite a lot — workflow packages with manifests and activation rules, automatic workflow selection, a plan lifecycle, Context Vault, Twilight Mountains — but it is hard for us to see what a user actually gets that upstream PI-Desktop does not, and how it makes their experience better.

If you can describe it as concrete user-visible behaviour — "here is the workflow, here is what the user sees, here is why it is better" — we would genuinely like to read it, and a focused PR against upstream is the most likely way for any of it to reach users. A fork-wide change set is very hard for us to review or maintain, so small, clearly motivated PRs will land far faster.

Thanks again for taking the time — we are interested in where this goes.

[Akshayxkill]

I’ve made quite a few improvements, but it isn’t exactly what I envisioned yet. If you want to see exactly how it improves the base version of pi-desktop, you can clone the repo and try it yourself, or ask other users to do the same. Right now I won’t give a brief, but I’ll do so when the app is much better and closer to my vision.
About the themes i will make a pull request soon regarding the app since it right now does not support a plugin theme which would use an image as a backdrop. i want to make those changes so these themes can be a part of orignal pi-desktop too
not sure since it'll probably will take time but we'll see

[vastsa]

I’ve made quite a few improvements, but it isn’t exactly what I envisioned yet. If you want to see exactly how it improves the base version of pi-desktop, you can clone the repo and try it yourself, or ask other users to do the same. Right now I won’t give a brief, but I’ll do so when the app is much better and closer to my vision. About the themes i will make a pull request soon regarding the app since it right now does not support a plugin theme which would use an image as a backdrop. i want to make those changes so these themes can be a part of orignal pi-desktop too not sure since it'll probably will take time but we'll see

It sounds like you’ve already put a lot of thought and work into this, and I really appreciate the effort you’ve made to push the experience beyond the base version of PI-Desktop.

No need to rush the brief — I’d rather see the full vision once you feel it’s ready.

And yeah, the theme limitation you mentioned is definitely something worth improving. If you want to add support for image-based backdrops through the plugin theme system, feel free to open a PR when you’re ready. I’d be happy to review it and see how we can make it fit cleanly into the original PI-Desktop architecture.

Take your time with it — no pressure. I’m genuinely curious to see where you take it.