Skip to main content

​
Configure Widget

This panel controls the user-facing widget experience. You can customize:
  • widget name
  • widget behavior (overlay or push)
  • widget icon
  • appearance mode (infer from host page or custom theme)
  • input placeholder
  • empty state title and description
  • starter suggestions
  • security disclosure visibility

​
Appearance Modes

​
Infer from host page

This is the default mode.
  • the widget reads your dashboard’s colors and typography at runtime
  • no preview is shown in Warpy because the dashboard shell cannot truthfully reproduce the customer’s app
  • existing embeds keep this behavior automatically

​
Custom theme

Use this when you want deterministic styling instead of runtime inference.
  • define explicit light and dark themes
  • adjust colors, typography, layout, and shadows with live controls
  • preview changes instantly in a production-identical preview powered by the real widget runtime
  • switch preview scenes to inspect closed launcher, empty chat, starter suggestions, screen autopilot, messages, and the security drawer
The preview is interactive for launcher, close, scene changes, and the security panel, but it does not send messages or execute real actions.

​
Overlay vs push

The widget opens above the page. Use this when you want minimal layout disruption.

The widget makes room in the page. Use this when preserving visible app context matters more than strict overlay behavior.

​
White-labeling guidance

Replace the default widget name and icon with the customer’s product context before end users see it.

​
Suggestions

Starter suggestions are the short prompts shown in an empty chat. They should be:
  • short
  • clickable
  • action-oriented
  • written in end-user language
Examples:
  • “Show recent invoices”
  • “Create a refund”
  • “Summarize open approvals”

​
Chat navigation

Long conversations keep their place automatically:
  • if new assistant messages arrive while the panel is closed, the launcher shows them as unread
  • reopening lands at the first unread message instead of the middle of the thread
  • a visible New divider marks where unread content starts
  • if the user is reading older messages, the widget shows a down-arrow jump control instead of forcing the view to move
This makes the widget behave more like a mature chat timeline without changing the customer-facing setup.

​
Custom Instructions

Custom Instructions define the assistant’s:
  • personality
  • knowledge boundaries
  • tone
  • response style
Use this area to shape how the agent speaks inside the customer’s product, not to restate technical implementation details. Good instruction traits:
  • concise
  • product-specific
  • non-technical unless the audience is technical
  • explicit about when to give step-by-step help
  • explicit about when to avoid guessing

​
Screen Autopilot

Screen autopilot lets the agent:
  • read the page context
  • find elements
  • execute UI actions
  • fall back to JavaScript execution when necessary
It does not require your manually defined frontend tools. Use it when:
  • your UI already contains the action but you have not exposed a dedicated tool
  • the action is easier to perform through the live page
  • users need page-level guidance, not just API execution

​
When to prefer a manual frontend tool instead

Prefer a manual frontend tool when:
  • the action already exists as a stable client-side handler
  • you need a strongly controlled, deterministic browser action
  • you want framework-aware state changes instead of UI inference