Title: Context Assistant
Author: contextassistant
Published: <strong>2026 年 8 月 7 日</strong>
Last modified: 2026 年 8 月 7 日

---

搜尋外掛

![](https://ps.w.org/context-assistant/assets/banner-772x250.png?rev=3638014)

![](https://ps.w.org/context-assistant/assets/icon-256x256.png?rev=3638014)

# Context Assistant

 由 [contextassistant](https://profiles.wordpress.org/contextassistant/) 開發

[下載](https://downloads.wordpress.org/plugin/context-assistant.0.1.0.zip)

 * [詳細資料](https://tw.wordpress.org/plugins/context-assistant/#description)
 * [使用者評論](https://tw.wordpress.org/plugins/context-assistant/#reviews)
 *  [安裝方式](https://tw.wordpress.org/plugins/context-assistant/#installation)
 * [開發資訊](https://tw.wordpress.org/plugins/context-assistant/#developers)

 [技術支援](https://wordpress.org/support/plugin/context-assistant/)

## 外掛說明

Context Assistant adds an AI chat widget to your site — but unlike a
 generic chatbot,
it is built around three ideas:

 * **Page context.** The assistant knows _where_ the visitor is: which
    post or 
   product is open, its title and categories. Never the page body, never form input,
   never cookies — only small facts you allow.
 * **Answers from your content.** Published posts, pages and products
    are synced
   into a knowledge base; the assistant answers questions about _your_ site, grounded
   in retrieval, not model memory.
 * **Safe actions.** The assistant can act — search content, draft
    posts, check
   a customer’s own order, update stock — always with the signed-in user’s own WordPress
   capabilities, and any change only after an explicit preview card and an Apply
   click. Deletions need a second confirmation and go to the trash, never permanent
   removal.

The heavy lifting (models, retrieval, orchestration) runs on a Context
 Assistant
server; this plugin connects your site to it. Your secret API key is encrypted at
rest and never leaves your server — visitors only ever hold short-lived tokens.

**WooCommerce:** with WooCommerce active, the assistant additionally
 searches the
catalog with live prices and stock, shows a signed-in customer the status of their
own orders, and lets shop managers update stock through the preview/Apply flow.

**For developers:** add your own assistant tools with the
 context_assistant_tools
filter, extend the page context with context_assistant_page_context, and control
widget visibility with context_assistant_should_render. WP-CLI: `wp context-assistant
sync`.

### External services

This plugin does not work on its own: the models, retrieval and
 orchestration run
on a **Context Assistant server** that you configure in **Settings  Context Assistant**(
the API URL). That server is either your own self-hosted instance or the hosted 
Context Assistant service — the plugin talks only to whichever URL you enter.

What the plugin sends to that server, and when:

 * **When a visitor opens the chat** — a short-lived embed token is
    minted for 
   the browser, and the page context you allowed (page URL, titles, public taxonomy
   terms; each behind its own privacy toggle, never the page body or form input)
   is attached to the conversation.
 * **On each message** — the visitor’s message text and that page
    context, so the
   assistant can answer. Visitors are identified by an anonymous cookie, not by 
   name.
 * **When knowledge sync is enabled** — the text of your _published_
    posts, pages
   and products (never drafts or private content), so the assistant can answer from
   your own content.
 * **When the Remote Tools bridge is enabled** — the server calls back
    into your
   site to run tools under the signed-in user’s own WordPress capabilities; your
   secret API key stays encrypted on your server and is never sent to the browser.

Conversation transcripts are stored on that server and can be exported
 or deleted(
see the FAQ). No data is sent anywhere else.

If you use the **hosted** Context Assistant service, it is operated
 under its own
terms of service and privacy policy: Terms: https://contextassistant.io/terms/ Privacy:
https://contextassistant.io/privacy/

## 螢幕擷圖

[⌊A visitor asks in plain language; the answer is grounded in the site's own published
pages. The page body itself is never sent — only the small facts you allow.⌉⌊A visitor
asks in plain language; the answer is grounded in the site's own published pages.
The page body itself is never sent — only the small facts you allow.⌉[

A visitor asks in plain language; the answer is grounded in the site’s own published
pages. The page body itself is never sent — only the small facts you allow.

[⌊Anything that changes the site stops at a preview card first and runs only after
an explicit Apply, under the signed-in user's own WordPress capabilities.⌉⌊Anything
that changes the site stops at a preview card first and runs only after an explicit
Apply, under the signed-in user's own WordPress capabilities.⌉[

Anything that changes the site stops at a preview card first and runs only after
an explicit Apply, under the signed-in user’s own WordPress capabilities.

[⌊Settings: one connection check for the API, the assistant and the bridge. The 
secret key is stored encrypted and never shown again.⌉⌊Settings: one connection 
check for the API, the assistant and the bridge. The secret key is stored encrypted
and never shown again.⌉[

Settings: one connection check for the API, the assistant and the bridge. The secret
key is stored encrypted and never shown again.

[⌊The setup wizard asks for three values from your console and nothing else.⌉⌊The
setup wizard asks for three values from your console and nothing else.⌉[

The setup wizard asks for three values from your console and nothing else.

[⌊Insights: usage and real conversation transcripts, without leaving wp-admin.⌉⌊
Insights: usage and real conversation transcripts, without leaving wp-admin.⌉[

Insights: usage and real conversation transcripts, without leaving wp-admin.

## 適用於區塊編輯器

這個外掛提供 1 個可供區塊編輯器使用的區塊。

 *   Context Assistant Shows the Context Assistant chat widget on this page (useful
   when the widget is limited to selected post types).

## 安裝方式

 1. Install and activate the plugin.
 2. Open **Settings  Context Assistant**.
 3. Enter your API URL, secret key (`ca_sk_…`) and Assistant ID from the Context Assistant
    console, and make sure your site’s origin is allow-listed on the assistant.
 4. Press **Check connection** — three green checks mean the widget is live on your
    site.
 5. Optional: enable **Knowledge base sync** so the assistant answers from your content,
    and the **Remote Tools bridge** so it can act.

## 常見問題集

### Which key goes into the settings?

The Context Assistant secret key (`ca_sk_…`) from your console. The AI
 provider
key (e.g. an OpenAI `sk-…` key) is configured on the Context Assistant server and
never enters WordPress.

### What data does the widget send?

Per message: the page URL, titles and public taxonomy terms — each
 behind its own
toggle, and never the page body. The knowledge base sync sends only published content.
Visitors are identified by an anonymous cookie; the plugin sets no tracking cookies
beyond it.

### Does it work with page caching?

Yes. Anonymous pages carry nothing user-specific — tokens are fetched
 by the browser
after the page loads, so full-page caches keep working.

### Can visitors change my site through the assistant?

No. Guests only see read-only tools over already-public content.
 Mutating tools
exist only for signed-in users with the matching WordPress capabilities, and every
mutation requires an explicit confirmation in the chat.

### Can I export or delete the conversation history?

Yes. Transcripts are stored on the Context Assistant server, not in
 your WordPress
database. The server exposes an export of all conversations and deletion of any 
single conversation, so a visitor’s data can be handed over or erased on request(
GDPR). Self-hosting the server keeps that data entirely under your control — see
below.

### Where are the widget’s readable sources?

The plugin enqueues a minified `assets/embed.js`. Its full, unminified
 source ships
beside it as `assets/embed.src.js`, and both are built from `packages/embed-sdk`
in the public repository — no build step is hidden.

## 使用者評論

這個外掛目前沒有任何使用者評論。

## 參與者及開發者

以下人員參與了開源軟體〈Context Assistant〉的開發相關工作。

參與者

 *   [ contextassistant ](https://profiles.wordpress.org/contextassistant/)
 *   [ sandra1n ](https://profiles.wordpress.org/sandra1n/)

[將〈Context Assistant〉外掛本地化為台灣繁體中文版](https://translate.wordpress.org/projects/wp-plugins/context-assistant)

### 對開發相關資訊感興趣？

任何人均可[瀏覽程式碼](https://plugins.trac.wordpress.org/browser/context-assistant/)、
查看 [SVN 存放庫](https://plugins.svn.wordpress.org/context-assistant/)，或透過 
[RSS](https://plugins.trac.wordpress.org/log/context-assistant/?limit=100&mode=stop_on_copy&format=rss)
訂閱[開發記錄](https://plugins.trac.wordpress.org/log/context-assistant/)。

## 變更記錄

#### 0.1.0

 * Initial release: chat widget with page context, embed-token security,
    knowledge
   base sync (RAG), 25 capability-scoped WordPress and WooCommerce tools, and a 
   WP-CLI sync command.

## 中繼資料

 *  版本 **0.1.0**
 *  最後更新 **3 週前**
 *  啟用安裝數 **少於 10 次**
 *  WordPress 版本需求 ** 6.2 或更新版本 **
 *  已測試相容的 WordPress 版本 **7.0.4**
 *  PHP 版本需求 ** 8.0 或更新版本 **
 *  語言
 * [English (US)](https://wordpress.org/plugins/context-assistant/)
 * 標籤:
 * [AI](https://tw.wordpress.org/plugins/tags/ai/)[assistant](https://tw.wordpress.org/plugins/tags/assistant/)
   [chat](https://tw.wordpress.org/plugins/tags/chat/)[chatbot](https://tw.wordpress.org/plugins/tags/chatbot/)
   [woocommerce](https://tw.wordpress.org/plugins/tags/woocommerce/)
 *  [進階檢視](https://tw.wordpress.org/plugins/context-assistant/advanced/)

## 評分

這個項目尚無任何評論記錄。

[撰寫評分](https://wordpress.org/support/plugin/context-assistant/reviews/#new-post)

[查看全部使用者評論](https://wordpress.org/support/plugin/context-assistant/reviews/)

## 參與者

 *   [ contextassistant ](https://profiles.wordpress.org/contextassistant/)
 *   [ sandra1n ](https://profiles.wordpress.org/sandra1n/)

## 技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

 [檢視技術支援論壇](https://wordpress.org/support/plugin/context-assistant/)