Title: Npcink Cloud Addon Author: Npcink Published: 2026 年 6 月 22 日 Last modified: 2026 年 7 月 13 日 --- 搜尋外掛 ![](https://ps.w.org/npcink-cloud-addon/assets/banner-772x250.png?rev=3582534) ![](https://ps.w.org/npcink-cloud-addon/assets/icon-256x256.png?rev=3582534) # Npcink Cloud Addon 由 [Npcink](https://profiles.wordpress.org/muze233/) 開發 [下載](https://downloads.wordpress.org/plugin/npcink-cloud-addon.0.1.3.zip) * [詳細資料](https://tw.wordpress.org/plugins/npcink-cloud-addon/#description) * [使用者評論](https://tw.wordpress.org/plugins/npcink-cloud-addon/#reviews) * [安裝方式](https://tw.wordpress.org/plugins/npcink-cloud-addon/#installation) * [開發資訊](https://tw.wordpress.org/plugins/npcink-cloud-addon/#developers) [技術支援](https://wordpress.org/support/plugin/npcink-cloud-addon/) ## 外掛說明 Npcink Cloud Addon connects a local WordPress site to `npcink-cloud`. It stores the Cloud Base URL and Cloud API Key, parses Cloud-issued keys, signs runtime requests, probes health, reads Cloud entitlement summaries, and can upload metadata-only plugin behavior events after explicit administrator opt-in. It does not execute WordPress writes, approve proposals, own billing truth, or manage prompts, routers, presets, workflow/task queues, scheduler truth, or workflow engines. Its observability buffer is only a bounded delivery buffer for monitoring metadata and is not Core audit, proposal, execution, billing, or workflow truth. For media derivative jobs, local host code may pass the read-only npcink-abilities- toolkit/build-media-derivative-cloud-request ability output and a short TTL source artifact descriptor to the addon for signed Cloud dispatch. The addon requires verified Cloud settings, rejects credential-bearing ability payloads, and returns proposal- ready data with `final_write_owner=local_wordpress_host`. Final review, recording, replacement, rollback, and WordPress writes remain in the local host/Core approval path. For plugin monitoring, the addon may upload operational metadata such as plugin slug/version, event kind, status, timing, error code, route, proposal id, ability id, correlation id, and counters. It must not upload prompts, generated content, article body content, media bytes, raw request or response payloads, provider credentials, Cloud API secrets, passwords, cookies, nonces, Authorization headers, database names, table names, or filesystem paths. ### External Services This plugin connects to the Npcink Cloud service configured by the site administrator through the Cloud Base URL setting. The plugin contacts the configured Cloud service only after an administrator enters a Cloud Base URL and Cloud API Key, saves the settings, verifies the connection, or a local Npcink component explicitly uses the Cloud runtime client. Requests may include the configured site identifier, key identifier, request timestamp, nonce, trace identifier, idempotency key, HMAC signature headers, runtime request payloads supplied by local Npcink components, metadata-only monitoring events when enabled, and read-only requests for health, run status, run result, usage statistics, entitlement summaries, observability summaries, and Agent feedback quality summaries. The stored Cloud API Key secret is used server-side for request signing and is not printed in wp-admin. For host-supplied media derivative runtime jobs, requests may also include a short TTL source artifact descriptor and derivative request parameters from the local read-only ability output. Cloud credentials and signed headers are added by the addon transport and are not copied into the ability payload. For Site Knowledge transport, requests may include public post/page identifiers, public content manifest metadata, approved comment change hints, local delivery consent state, and explicit administrator delivery intents for Cloud-owned index operations. Drafts, private posts, password-protected posts, credentials, and raw database fields must not be sent by this transport. The Site Knowledge change bridge health seam returns site_knowledge_change_bridge_status. v1. Local consumers should surface it as change_bridge and treat `buffer_count` as bounded delivery-buffer depth only, not queue truth, freshness truth, index lifecycle truth, or Cloud diagnostics truth. For WordPress AI connector scene runtime, image context evidence, Runtime Runs detail, artifact preview download, and Agent feedback event transport, requests may include the bounded scene request, media URL or artifact descriptor, run id, artifact id, or local operator feedback metadata needed for that specific Cloud runtime/read endpoint. The addon does not create Core proposals, approve changes, execute WordPress writes, own retry queues, or own Site Knowledge index lifecycle. The configured Cloud service is responsible for its own privacy policy, terms of service, data retention, and account/key issuance. Because the Cloud Base URL is administrator-configured, site administrators should only connect this plugin to a Cloud service whose terms of service, privacy policy, data retention policy, and account/key issuance process they have reviewed. Npcink Cloud service information: * Terms of Service: https://cloud.npc.ink/terms/en/terms.html * Privacy Policy: https://cloud.npc.ink/terms/en/privacy.html * Data Retention: https://cloud.npc.ink/terms/en/data-retention.html ## 螢幕擷圖 [⌊Verified connector overview with compact plan, points, and Site Knowledge article capacity.⌉⌊Verified connector overview with compact plan, points, and Site Knowledge article capacity.⌉[ Verified connector overview with compact plan, points, and Site Knowledge article capacity. [⌊Local permissions for WordPress AI and Site Knowledge delivery.⌉⌊Local permissions for WordPress AI and Site Knowledge delivery.⌉[ Local permissions for WordPress AI and Site Knowledge delivery. [⌊Site Knowledge delivery status and bounded Cloud-owned index actions.⌉⌊Site Knowledge delivery status and bounded Cloud-owned index actions.⌉[ Site Knowledge delivery status and bounded Cloud-owned index actions. [⌊Advanced troubleshooting with service detail, runtime runs, and connection recovery.⌉⌊ Advanced troubleshooting with service detail, runtime runs, and connection recovery .⌉[ Advanced troubleshooting with service detail, runtime runs, and connection recovery. ## 安裝方式 1. Place this directory in `wp-content/plugins/npcink-cloud-addon`. 2. Activate `Npcink Cloud Addon`. 3. Open `Npcink AI > Cloud Addon`, or `Settings > Npcink Cloud Addon` when the addon is installed standalone. 4. Enter Cloud Base URL and Cloud API Key. 5. Click `Save and Verify`. ## 常見問題集 ### Does this plugin create Cloud API Keys? No. Keys are issued by Npcink Cloud. ### Do I need a Npcink Cloud account? Yes. A site administrator needs a Cloud Base URL and a Cloud API Key issued by the configured Npcink Cloud service before the connector can verify successfully. ### Does this plugin display the Cloud secret? No. The secret is stored for server-side signing only and is never printed on the settings page. ### When does the plugin contact Npcink Cloud? The plugin contacts the configured Cloud service when an administrator saves and verifies Cloud settings, when a local Npcink component explicitly uses the Cloud runtime client, when entitlement or status summaries are refreshed, or when optional monitoring is enabled and flushed. ### Is monitoring enabled by default? No. Monitoring requires explicit administrator opt-in and verified Cloud settings. ### What data can monitoring send? Monitoring sends operational metadata only, such as plugin slug/version, event kind, status, timing, error code, route, proposal id, ability id, correlation id, counters, and latency. ### Does monitoring upload prompts, content, or raw payloads? No. Metadata-only monitoring is designed not to upload prompts, generated content, article body content, media bytes, raw request or response payloads, provider credentials, Cloud API secrets, passwords, cookies, nonces, Authorization headers, database names, table names, or filesystem paths. ### Can media derivative jobs send media data to Cloud? Only when local host code explicitly invokes the media derivative transport. In that case, the request may include a short TTL source artifact descriptor and bounded derivative parameters from a local read-only ability output. Cloud credentials and signed headers are added by the addon transport and are not copied into the ability payload. ### Does this plugin write Cloud recommendations into WordPress? No. Final WordPress writes must go through local Core proposal, preflight, approval, and apply paths. ### Where can I review the Cloud service terms and privacy information? Terms of Service: https://cloud.npc.ink/terms/en/terms.html Privacy Policy: https://cloud.npc.ink/terms/en/privacy.html Data Retention: https://cloud.npc.ink/terms/en/data-retention.html ## 使用者評論 這個外掛目前沒有任何使用者評論。 ## 參與者及開發者 以下人員參與了開源軟體〈Npcink Cloud Addon〉的開發相關工作。 參與者 * [ Npcink ](https://profiles.wordpress.org/muze233/) 〈Npcink Cloud Addon〉外掛目前已有 1 個本地化語言版本。 感謝[全部譯者](https://translate.wordpress.org/projects/wp-plugins/npcink-cloud-addon/contributors) 為這個外掛做出的貢獻。 [將〈Npcink Cloud Addon〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/npcink-cloud-addon) ### 對開發相關資訊感興趣？ 任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/npcink-cloud-addon/)、 查看 [SVN 存放庫](https://plugins.svn.wordpress.org/npcink-cloud-addon/)，或透過 [RSS](https://plugins.trac.wordpress.org/log/npcink-cloud-addon/?limit=100&mode=stop_on_copy&format=rss) 訂閱[開發記錄](https://plugins.trac.wordpress.org/log/npcink-cloud-addon/)。 ## 變更記錄 #### 0.1.3 Simplify the admin overview and Site Knowledge quota display, align localized quota copy, harden Cloud authorization redirects, and refresh release assets. #### 0.1.2 Refine bounded Site Knowledge Cloud transport, WordPress AI connector request-log compatibility, Cloud runtime contract reuse documentation, and Plugin Check release validation. #### 0.1.1 Refresh Cloud connection status actions, entitlement summary caching, WordPress AI connector integration, zh_CN strings, and release packaging checks. #### 0.1.0 Initial standalone connector skeleton. ## 中繼資料 * 版本 **0.1.3** * 最後更新 **4 天前** * 啟用安裝數 **少於 10 次** * WordPress 版本需求 ** 7.0 或更新版本 ** * 已測試相容的 WordPress 版本 **7.0.2** * PHP 版本需求 ** 8.0 或更新版本 ** * 語言 * [Chinese (China)](https://cn.wordpress.org/plugins/npcink-cloud-addon/) 及 [English (US)](https://wordpress.org/plugins/npcink-cloud-addon/). * [將這個外掛本地化為你的母語版本](https://translate.wordpress.org/projects/wp-plugins/npcink-cloud-addon) * 標籤: * [cloud](https://tw.wordpress.org/plugins/tags/cloud/) * [進階檢視](https://tw.wordpress.org/plugins/npcink-cloud-addon/advanced/) ## 評分 這個項目尚無任何評論記錄。 [Your review](https://wordpress.org/support/plugin/npcink-cloud-addon/reviews/#new-post) [查看全部使用者評論](https://wordpress.org/support/plugin/npcink-cloud-addon/reviews/) ## 參與者 * [ Npcink ](https://profiles.wordpress.org/muze233/) ## 技術支援 使用者可在技術支援論壇提出意見反應或使用問題。 [檢視技術支援論壇](https://wordpress.org/support/plugin/npcink-cloud-addon/)