> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glasswarp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Eyes and hands

> The one idea behind Glasswarp — and the line between platform and agent.

Glasswarp gives an AI agent **eyes and hands on a real Windows machine**. That's
the whole product. You bring the **brain**.

## The split

<Columns cols={2}>
  <div>
    ### 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
  </div>

  <div>
    ### 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.
  </div>
</Columns>

## 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

<Note>
  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, sub-30 ms,
  GPU-accelerated, with structured UIA targets so clicks land in real controls.
</Note>

Continue to [Rigs and sessions](/concepts/rigs-and-sessions).