Sees the whole interface
Every window, list, field and menu the application is made of, with the values they currently hold. Not a screenshot of them - the things themselves.
Iniscape Control
In development
Drive an application from the inside.
Iniscape Control operates a desktop application through its own interface - the actual buttons, fields and menus it is built from, rather than pixels on a screen. Automate a task you repeat, or exercise an interface that has to keep working.
Iniscape Control is not released yet. Tell us which application you want to drive and we will write to you when there is a build to try.
What it does
Real controls, not coordinates.
Acts the way the app does
Pressing a button runs what the application would have run itself. A moved window, a different theme or a resized dialog changes nothing.
Nothing to add to the app
Iniscape Control attaches to software as it ships. No source changes, no rebuild, no cooperation needed from whoever wrote it.
Scripted or asked
The same set of commands serves a script you wrote and an AI assistant you talk to. One surface, two ways of reaching it.
Record, then replay
Do the job once by hand and get it written down as steps. Run those steps again whenever you need them, unattended.
Waits for the right moment
A step can wait until the interface is genuinely ready rather than for a fixed number of seconds. That is most of the difference between automation you trust and automation you rerun.
How it works
Attach, capture, run.
Attach
Point Iniscape Control at an application, running or not. It reads the interface without touching anything until you ask it to.
Capture
Perform the task once yourself and have it written down, or describe what you want and let an assistant work it out.
Run
Replay it - from your own script, from a build pipeline, or on demand. The same steps, the same result, every time.
Why it holds up
Automation that survives the next release.
Most UI automation breaks because it describes where things were rather than what they are. Iniscape Control describes what they are.
A layout change is not a failure
A step names a control, so moving it, restyling it or putting it on another row does not break the run.
The same run, twice
Replay is deterministic, so a difference between two runs is a finding rather than noise from the harness.
For your app or somebody else’s
Test the interface you are building, or automate a tool you merely have to use. Both are the same job to Iniscape Control.
Which application would you point it at?
Iniscape Control is still in development, and the first edition will cover one family of desktop applications before it covers others. Tell us what you want to drive - it helps decide the order.