See how the assistant helps on the page where the task actually happens
Help a shopper choose, a reader understand, or a site owner make a safe change. Pick a scenario and follow the conversation from page context to outcome.
Availability depends on the integration you choose and the visitor or owner's real permissions.
Find a compatible product
The assistant recommends only in-catalog, compatible parts — never a guess from the model alone.
A shopper is on a technical product page where compatibility matters more than a general FAQ answer.
Two real, in-stock, compatible items — with price and availability pulled from the catalog.
- Page context ruled out incompatible AM5/DDR5 options before any search ran.
- search_products and get_product read the live catalog — no invented items.
- Both are read-only tools: they run automatically, no confirmation needed.
Technical details
Tools: search_products, get_product
Check my order status
The visitor gets a real status update, and a different customer’s order stays invisible — not even its existence leaks.
A signed-in customer wants an order update without digging through email or contacting support.
A live status straight from the store, with cross-account access refused outright.
- get_order_status runs only against the signed-in customer’s own identity.
- A foreign order returns the same refusal as a non-existent one — existence never leaks.
- No tracking number is shown unless the store’s own tool actually returns one.
Technical details
Tools: get_order_status
Understand the current article
A grounded answer with clickable citations, not a hallucinated summary.
An article is long or uses internal terminology, and the reader wants a direct answer sourced from the site itself.
A short, sourced explanation plus a pointer to the next relevant piece of content.
Источники:
• Standard vs Advanced modes
• Security model
- Current-page context helps interpret what "Advanced" refers to on this specific site.
- The answer is grounded in synced content, not the model’s general knowledge.
- Citations link straight back to the host’s own pages.
Technical details
Tools: search_content
Get help on the current screen
The assistant already knows which integration and error are on screen — no screenshot needed.
A user is stuck on an integration-settings screen, and a generic knowledge base doesn’t know which provider or status is currently open.
A direct diagnosis and a one-click path to the fix, grounded in the actual screen state.
Fix the domain under Install → Allowed origins, then re-run the check.
- The host builds a structured screen context itself — the assistant never scrapes the DOM.
- No hidden input values or closed-form fields are ever included.
- The fix link is a host-defined navigation action, not a guess.
Technical details
Tools: get_screen_context (custom)
Reschedule a booking
A real proposed change, shown before anything is saved to the booking system.
A client wants to move an existing appointment without a phone call, on a site whose booking backend is entirely custom.
A confirmed new time, applied only after the client explicitly approves it.
Запись перенесена на пятницу, 16:30. Подтверждение отправит сам booking host.
- Context Assistant orchestrates the conversation and the confirmation step.
- Availability, booking rules and notification delivery all belong to the client’s own system.
- Nothing is written until the client picks a specific slot and approves it.
Technical details
Tools: get_availability (custom), update_booking (custom)
Update product stock
A visible before/after, applied to the real store only after Apply.
The owner is already looking at a product or working the shop floor and needs a quick stock change without opening wp-admin.
Stock and status updated, with the change recorded in the action log.
Изменение применено.
Recorded in the action log · request req_…
- search_products and get_product ran automatically to find the item.
- update_product_stock is a write tool — it waited for an explicit Apply.
- The action is recorded in the audit log with a request ID.
Technical details
Tools: search_products, get_product, update_product_stock
Create a draft from notes
A structured draft, never auto-published.
An editor already has rough notes and wants a starting structure without publishing anything by accident.
A new draft post, ready to open and refine in the editor.
Черновик создан. Открыть его в редакторе?
- create_draft_post can never set status to published — the field doesn’t exist in its write scope.
- The editor keeps full control to revise before publishing.
Technical details
Tools: create_draft_post
Moderate and answer comments
Reads run instantly; every moderation action is still its own confirmed step.
An editor has a backlog of comments awaiting moderation and wants to triage quickly.
Spam cleared, real questions answered — each as a distinct, confirmed action.
Marked as spam. This can be restored from WordPress spam.
- list_comments is a read — it runs without confirmation.
- spam_comment and reply_to_comment are separate write tools, each with its own preview — never bundled into one opaque button.
- A reply is published under the moderator’s own name, nested under the parent comment.
Technical details
Tools: list_comments, spam_comment, reply_to_comment
Move old media to trash
The delete policy in action: preview, a second confirmation, and a real Restore path.
An editor is cleaning up old assets and wants to remove one safely, without a silent, unrecoverable delete.
The file moves to WordPress’s own trash — recoverable, not erased.
Переместить файл в корзину?
Moved to trash. Restore from WordPress trash any time.
- trash_media never permanently deletes — WordPress’s own trash is the recovery window.
- A second, explicit confirmation stands between preview and the actual move.
- The preview surfaces the one page that references this file before you decide.
Technical details
Tools: get_media, trash_media
Review a sales summary
A fast, read-only answer with no separate dashboard detour.
The owner wants a quick read on recent performance while already working in the store.
A real number pulled straight from WooCommerce, exactly as the store itself returns it.
- get_sales_summary requires view_woocommerce_reports — it is not public.
- It is a read tool: no confirmation needed, but gated to the right capability.
- No period-over-period comparison is invented — only what the tool actually returns.
Technical details
Tools: get_sales_summary
Update a support ticket
A visible before/after on a fully custom backend — the same contract as every other integration.
A support lead is triaging tickets and wants to reassign and re-prioritize without leaving the conversation.
The ticket updated in the client’s own system, confirmed before it happens.
Ticket updated.
- The tool and its permission model are defined entirely by the client’s backend.
- Context Assistant never receives an operator credential in the browser.
- One integration reuses the same four endpoints — /tools, /context, /tools/preview, /tools/execute — as every other Remote Tools host.
Technical details
Tools: update_ticket (custom)