Korean / 한국어

출판 플러그인 카탈로그 및 설치 .piplug 패키지 PI-데스크탑.

**Plugin 소스는 여기에 호스팅되지 않고 더 이상 허용되지 않는 요청을 당겨. ** 소스는 저자의 자신의 저장소에 살고 각 릴리스는 플러그인 센터를 통해 간다 — plugins.aiuo.net — 클라이언트의 기본 카탈로그 소스입니다. 전 plugins/ 나무가 제거되었습니다. 플러그인을 발송하려면, 읽기 플러그인 게시.

플러그인 게시

# # 1. 자신의 저장소에 구축

앱 내 템플릿에서 시작: Plugins → 템플릿에서 새로운 플러그인 (panel-basic, agent-tool-basic], skill-pack], full-demo). PI-Desktop에서 devkit CLI를 사용할 수도 있습니다.

Plugins → Load dev 플러그인를 사용하여 폴더를 로드합니다. 포장 .piplug with Install 플러그인 패키지 당신이 그것을 출시하기 전에. 전체장편 계약 (manifest schema, host API, permissions, security) 문서화 docs/plugin-development.md].

##2. 플러그인 센터에 게시

둘 다 노선은 동일한 backend를 도달합니다:

• Console — 플러그인에 로그인합니다.aiuo.net → ** 내 플러그인** →

PI-Desktop Plugins

中文版 / Chinese

The published plugin catalog and the installable .piplug packages for PI-Desktop.

Plugin sources are not hosted here and pull requests that add them are no longer accepted. Sources live in their authors’ own repositories and every release goes through the plugin center — plugins.aiuo.net — which is the client’s default catalog source. The former plugins/ tree was removed. To ship a plugin, read Publish a plugin.

Publish a plugin

1. Build it in your own repository

Start from a template inside the app: Plugins → ⋯ → New plugin from template (panel-basic, agent-tool-basic, skill-pack, full-demo). From a PI-Desktop checkout you can also use the devkit CLI:

pnpm --filter @pi-desktop/plugin-devkit... build
pnpm pi-plugin init panel-basic ../my.plugin-id
pnpm pi-plugin check ../my.plugin-id     # manifest, permissions, referenced files, size
pnpm pi-plugin pack ../my.plugin-id      # dist/my.plugin-id-0.1.0.piplug + SHA-256

Load the folder with Plugins → Load dev plugin while you work, and install the packed .piplug with Install plugin package before you release it. The full authoring contract (manifest schema, host API, permissions, security) is documented in docs/plugin-development.md.

2. Publish on the plugin center

Both routes reach the same backend:

• Console — sign in at plugins.aiuo.net → My Plugins → Create plugin: upload the package, bind the repository the plugin lives in, submit. Later versions are submitted from the plugin’s own page.

• AI client — install the publishing skill and let an agent run the whole flow:

  https://plugins.aiuo.net/skill.md
  

  The skill drives the MCP endpoint https://plugins.aiuo.net/mcp with a personal access token from Console → Tokens, kept at ~/.pi-desktop/plugin-center.token. It sends the fields of your local manifest.json plus the source files — ui, contributes, activationEvents, fs and net included, because anything a call omits is dropped and the installed plugin becomes invalid.

A release needs three things:

1. A tagged source repository. Push the plugin and tag the version (v0.4.8); the tag, or a commit SHA, becomes the sourceRef the source review reads.
2. A bound repository. The plugin is bound to one repository through the console’s source binding (a GitHub App grant). That binding is what the review and the catalog’s source pin follow, so it cannot be swapped afterwards without an operator.
3. A version nobody published before, with release notes. The center audits the source, an