Skip to main content
Glasswarp gives an agent eyes and hands on a Windows PC you own. You supply the brain. Treat full desktop control as powerful — start small, watch it, then open the throttle. Glasswarp handles session controls (consent, on-screen indicator, kill switch, audit, Live View). Your agent code handles what it’s allowed to do. See also: Safety and consent · Live View

Checklist

On the Glasswarp side

  • Use a dedicated rig when you can — not your everyday PC
  • Turn API access on only when you need it (Console → Rigs)
  • Scope API keys to one rig when possible
  • Keep Live View open on first runs; kill from Console if needed
  • Always end_session when finished

In your agent code

  • Ask a human before delete, send, purchase, install, or security changes
  • Allowlist apps the agent may launch
  • Set a max steps / max minutes budget
  • Don’t put passwords or secrets in prompts
  • Log what the agent is about to do

Simple split

You need both.

Patterns

Watch first. Open Live View (or the live_view_hitl template) before full autonomy. Confirm risky acts.
Budget + always clean up.

Console

In our examples

Helpers live in sdk/python/examples/safe_session.py (budgets, intent logs, allowlist, optional REQUIRE_CONFIRM=1). Templates and demos use them. Long showcases (Paint / Minesweeper) stay unattended by default — set REQUIRE_CONFIRM=1 if you want prompts.