Desktop control
Your AI controls each machine's desktop: it reads windows, clicks, types and takes screenshots. With one registry line in the image's recipe, it answers elevation prompts too.
How it works
Once your agent has its images, every test follows the same steps on the same kinds of machine.
The same six steps each time. The prompt tells your agent to give each run its own project name, so runs side by side keep to their own machines.
endia compose up --waitYour AI controls each machine's desktop: it reads windows, clicks, types and takes screenshots. With one registry line in the image's recipe, it answers elevation prompts too.
Your AI can test a server and its clients talking to each other, on a private network described in one Compose file.
Your AI writes image recipes in Dockerfile syntax, layering your runtimes and software over a Windows image you prepare once.
You authorise a client by generating a client certificate, using either the desktop app or endia context export at the CLI. You can revoke the certificate at any time.
# you, on the PC, when the agent asks
sbx policy allow network --sandbox <sandbox> localhost:7443
endia context export <sandbox>
# you, on the PC, to end its access
endia cert rm <sandbox>