Ask Kindly
Get contextual editing help, select elements, attach screenshots, and understand what the service receives.
Watch the video
Chapters and transcript Captions are included.
The chat icon in the bottom bar opens Ask Kindly. Point to something highlights native page elements and attaches up to five selections without activating links or changing content. Existing editor selection is reused on opening. Escape ends pointing; outside the help panel, editor keyboard handling remains unchanged.
Screenshot now reuses the canonical Cantata Site Feedback region-selection, capture, and annotation flow. Capture page area opens crosshairs with Capture full view, optional browser capture, and Cancel. The review dialog supports Highlight, Draw, annotation colors, Undo, Clear, Retake, and Attach to question. Uploads enter the same review dialog. Reopening an attachment preserves its capture diagnostics and editable annotations. Nothing is sent until the question is submitted.
DOM capture uses the feedback tool's document-origin rendering, scroll lock, image-size lock, content anchor correction and 24-million-pixel budget. The adapter also normalizes Kindly's desktop canvas zoom in the clone and maps crop coordinates back to the visible page. The editor and capture overlays are excluded from DOM screenshots. Use browser capture to include browser-rendered editor controls or content DOM rendering cannot reproduce. The browser chooser remains explicit, and capture tracks stop after capture. The attachment is capped below the help service's image limit; oversized images get an actionable retake message. No screenshot file is uploaded to WordPress media storage.
Questions go through the existing WordPress REST nonce and edit_post check. The server proxies to https://help.kindlyedit.com/ask using the installed license key. The browser never receives that key. The managed Worker verifies an active product license and activated site, limits requests, and calls Workers AI using a maintained behavior reference. Ask Kindly never runs model-generated code, and UI output uses textContent.
The service receives the question, recent conversation, selected element metadata, site URL, mode, and any explicitly attached screenshot. Selected elements contribute bounded visible text, image alt text, dimensions, and computed layout/typography settings. Context includes a page path without query or fragment, browser, viewport, screen dimensions, pixel ratio, and capture diagnostics. Form values, raw HTML, cookies, headers, and credentials are not collected. Screenshots remain explicit attachments. Neither WordPress nor the Worker persists conversations or images. Worker invocation logging is disabled; code does not log request headers or bodies. Rate limits are per authenticated license (20/minute) with a separate broad ingress limit (1000/minute per server IP). Platform limits are per location, not a global billing cap.
Changes Ask Kindly makes for you#
Ask Kindly can make a change in your draft: wording, a link, the order of a list, a style in the Desktop view and Normal state, or resetting a setting. It applies the change through the editor as one Undo step and briefly highlights what changed. Then choose Keep, Undo, Not quite (undo it and say what should be different), or Show change to see the highlight again. Nothing is saved or published by Ask Kindly; the change stays in your draft until you choose Save draft or Publish. The header, footer, forms and private areas are never changed. If a requested style change cannot apply in the current view, Ask Kindly says so and nothing changes.
Show me and Do it for me#
When an answer is a set of steps in the editor, Ask Kindly can offer Show me, which highlights each real control in turn and moves on when you use it, and Do it for me, which clicks those same controls for you while you watch. Do it for me only changes style choices, numbers with their units, and tick boxes, all as one step that Undo reverses. Code, conditions, forms and design classes stay yours, it never clicks Publish, Delete or similar actions, and a step that needs your own value is handed back to you. Known table questions, such as adding a row or column, use built-in guides that complete only after the table actually changes. Merged-cell tables, block-editor pages and permission restrictions can prevent a guide.
Development#
tests/context-help-browser.mjstests the UI against exact editor assets with a mocked answer route.tests/table-builder-browser.mjscovers the underlying table mutations.server/help-worker/test.mjstests auth, rate limits, input bounds, image restrictions and fail-closed errors.server/help-worker/wrangler.jsoncdeploys a separate service. It reads the existing license database without changing the update worker or license records.- The help service and the WordPress plugin are separately deployed. Matching editor assets and PHP routes must ship together.
Persistent selections and documentation#
Selected items stay purple with numbered dashed outlines while help is open, including after pointing ends and after each answer. A compact selection summary above the question expands to list or remove individual items. Multiple selections do not create chat messages. Overlays live in the editor UI only, follow layout and scroll changes, disappear on close, and remove disconnected elements. Up to five current selections accompany every follow-up. Paragraph and heading targets retain their semantic identity even when the pointer hits an inline child.
The service treats selected elements as the explicit subjects of the question. For a selected paragraph, an otherwise vague size question refers to its text size. The server supplies the authorized page title/type, active theme name, plugin version, publish/developer capabilities, and available theme guide/tokens. Sites can register public editor-facing documentation through cantata_edit_help_site_documentation (array, post ID). No private options or arbitrary site files are harvested. Missing site documentation remains unavailable, rather than invented. Site context is bounded to 16 KB.
server/help-worker/build-knowledge.mjs bundles 14 maintained product guides, excluding internal handoffs and proposals. knowledge.js includes the everyday guide plus relevant sections from the searchable corpus, bounded to about 44 KB. Build the reference when changing source documentation; npm run deploy and npm run check rebuild it automatically. Current verified Typography > Size instructions override older guide wording. This gives access to the product reference without pretending every site's undocumented behavior is known.
Common Developer-mode text-size and size-reset questions use exact documented answers after license/site validation, just as table actions do. Images, mixed nontext selections, box-dimension questions and Simple mode continue through contextual inference. This avoids contradictory alternatives for the verified native Typography controls.