CONTEXT ASSISTANT
Context Assistant compatibility with REEID Translate
Context Assistant compatibility with REEID Translate is being evaluated from available plugin evidence. Adds an AI chat widget that uses page context (post/product title and categories/taxonomy terms) without sending the page body or form input. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Context Assistant.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Context Assistant is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Context Assistant compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds an AI chat widget that uses page context (post/product title and categories/taxonomy terms) without sending the page body or form input.
- Sends a short-lived embed token to the browser when a visitor opens the chat, and attaches allowed page context to the conversation.
- On each chat message, transmits the visitor’s message text plus the allowed page context to the Context Assistant server for retrieval-grounded answers.
- Supports knowledge base sync that sends only published posts/pages/products text (not drafts/private content) to the Context Assistant server for answering.
- Provides a “Remote Tools bridge” mode where the server can call back into the WordPress site to run tools under the signed-in user’s WordPress capabilities, with mutations requiring explicit preview/Apply confirmation (and deletions requiring second confirmation and going to trash).
- Enqueues a minified frontend script `assets/embed.js` and ships an unminified source `assets/embed.src.js` (both built from `packages/embed-sdk`), indicating frontend script injection for the chat widget.
- Uses an anonymous cookie to identify visitors (per the provided evidence) and states it sets no tracking cookies beyond it.
CONTENT BOUNDARY
Context Assistant capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Context Assistant and REEID Translate FAQ.
What does Context Assistant do according to the available plugin evidence?
Context Assistant has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Context Assistant?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Context Assistant?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Context Assistant in a multilingual WordPress workflow.
REEID documents Context Assistant functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.