Notepad: UIA targets + type

The Windows-native structure story: an agent launches Notepad, finds the edit surface via UIA targets, and types — no pixel guessing.

launch_app → observe / list_targets (UIA) → click_target → type_text

Platform vs agent: Glasswarp provides eyes (observe / list_targets) and hands (click_target / type_text). Choosing Notepad and what to type is the agent.

Competitive frame: VNC only sees pixels. Here the host returns sparse click targets from Windows UI Automation, and native input lands in the real Win32 control.

Prerequisites

An online, API-enabled rig

See Install the host.

SDK installed

pip install glasswarp pillow
export GLASSWARP_API_KEY=gw_live_sk_...

Run

python sdk/python/examples/notepad_uia_demo.py

Env var	Default	Purpose
`NOTEPAD_PATH`	`C:\Windows\System32\notepad.exe`	App to launch
`DEMO_TEXT`	short hello line	Text typed into the editor
`GLASSWARP_BASE_URL`	Fly signaling URL	API gateway

What you’ll see

Rig: DESKTOP-… (…)
Session: …
  → launch_app C:\Windows\System32\notepad.exe
  → observe jpeg … targets=N
  → UIA edit target id=… role='edit' …
  → typed into Notepad; saved notepad_final.jpg
Result: ok

Artifacts: notepad_observe.jpg (SoM-marked when targets exist), notepad_final.jpg. Watch live via Console → Sessions → Eye.

Grounding

How UIA targets and Set-of-Mark make clicks reliable.

Paint: draw the wordmark Grounding: observe + Set-of-Mark

⌘I

Get started

Setup

Concepts

Guides

Examples

Help

Notepad: UIA targets + type

Prerequisites

Run

What you’ll see

Grounding

​Prerequisites

​Run

​What you’ll see

Grounding

Prerequisites

Run

What you’ll see