Skip to main content
Glasswarp gives an AI agent eyes and hands on a real Windows machine. That’s the whole product. You bring the brain.

​
The split

​
Glasswarp (eyes + hands)

  • Eyes — screenshot, observe, dirty rects, native-resolution JPEG
  • Hands — click, type_text, key_press, drag, move_mouse, scroll
  • Grounding — UIA targets and Set-of-Mark marks
  • A safe session — consent, on-screen indicator, kill switch, audit, Live View

​
You (the brain)

  • The model and prompts
  • CV, OCR, and solvers
  • Planning and the agent loop
  • What to click and what to type
Your task logic never runs in the platform.

​
Why it matters

This split keeps demos honest and integrations clean. When something drives Notepad or solves a board, the agent did it through the Glasswarp API — Glasswarp provided the transport, not the intelligence. Practically, it means:
  • You can swap models, prompts, and CV without touching the transport.
  • The platform stays a thin, fast, auditable I/O layer.
  • Safety controls live where they belong: around the session, not inside your agent’s decisions.

​
Versus a sandbox or VNC

A cloud sandbox gives you a fresh, throwaway Linux VM. VNC gives you a soft framebuffer where every click is a pixel guess. Glasswarp gives you the real Windows PC you own — native resolution, structured UIA targets so clicks land in real controls, and a Live View path that can use GPU encode when the host has NVENC. Agent observe/screenshot eyes are host capture + CPU JPEG (separate from the Live View media track). Glass-to-glass LAN latency under 30 ms is a mission target for Live View, not a published measurement.
Continue to Rigs and sessions and Safety and consent (including privacy and data flow).