Skip to main content

​
What Warpy is

Warpy is a configurable execution layer for B2B dashboards. It turns a natural-language request into one of four things:
  • a backend request your product already supports
  • a frontend action you expose in the host app
  • a direct page action through screen autopilot
  • a grounded answer from uploaded documents

​
The operating model

User intent
  -> Widget message
  -> Warpy orchestration
      -> Approved tools -> Execution in the host app
      -> Knowledge base search -> Grounded answer
      -> Screen autopilot -> Execution in the host app
  -> Assistant summary

​
Why the setup starts with API config

Warpy executes requests from the user’s browser. The first question is: where should requests go, and how should they authenticate? That is why the product starts with:
  1. base URLs
  2. session headers
  3. tools and features
  4. knowledge base
  5. activation and rollout

​
The four execution surfaces

Structured API calls sent to your configured base URL with session headers attached.

Manual browser handlers your app exposes through window.warpy(toolName, vars).

Built-in page reading and UI action execution when a manual tool does not exist.

Document retrieval for product knowledge, policy details, SOPs, or course material.

​
What happens after the user sends a message

  1. The widget sends the message to Warpy.
  2. Warpy decides whether to answer from documents, use an approved tool, or act on the page.
  3. If tool execution is needed, the widget executes the returned tool calls in the user’s browser.
  4. Tool results come back to Warpy.
  5. Warpy returns a final answer and optional follow-up suggestions.
While those browser-side tool calls are running, the widget does not only show a generic loader. It surfaces a live inline status card with a readable label for the current action. Manual backend tools and manual frontend tools both show this progress in the chat surface, and screen autopilot keeps its own richer step-by-step visibility. For the lower-level sequence, see Runtime flow.