Skip to main content

​
Give your agent eyes and hands on Windows

Glasswarp is the transport layer between your agent and Windows computers. It gives any model real-time vision and native input on Windows machines you or your clients already own — including no-API EHR, ERP, insurance AMS, and other licensed desktops. You bring the brain — the model, prompts, and task logic. Built for automation developers and small shops already doing that work; vertical AI teams building on the client’s PC are in scope.
Pair a Windows PC once. Your agent sees the screen and controls keyboard and mouse through one API — on the real desktop and apps your users run. No rented cloud PC required.

​
Start here

Quickstart

Connect the SDK, start a session, capture a frame, and send input in under five minutes.

Use with n8n

When the canvas hits a Windows app with no connector — HTTP Request, not a Glasswarp node.

Connect via MCP

Point Claude, Cursor, or any MCP client at Glasswarp — eyes and hands, no project code.

Setup for Agents

Paste one prompt into your coding agent and let it wire Glasswarp into your project.

Install the host

Put the host agent on a Windows machine, pair it, and enable API access.

API reference

Every /v1/* endpoint with an interactive request builder.

​
The loop

Every integration is the same shape: see the screen, decide, act, repeat. Glasswarp owns the see-and-act transport; your code owns the decide.

​
How Glasswarp differs

Typical computer-use sandboxes approximate a desktop (often Linux or a soft framebuffer). Glasswarp captures a real Windows machine with native input — your apps, your files, your GPU. Agent observe / screenshots use DXGI Desktop Duplication by default (GDI fallback) and are encoded as CPU JPEG; the GPU NVENC pipeline is used for Live View (the human watch stream), not the agent capture path. Details live in Eyes and hands and the FAQ on the marketing site.

​
Next