Shortening the Development Cycle by Handing QA Testing to an AI Agent — Design Notes for OpenAI GPT-6 Astra and Computer Use

Design notes for handing QA testing to an AI agent by pairing OpenAI's GPT-6 Astra with the Computer Use API, as of September 2026. A deterministic E2E suite and an exploratory AI tester serve different goals and run at different times. Placing the AI tester in four specific slots (the developer's local environment, running Codex alongside the ChatGPT desktop app's Computer Use; per-PR exploration; nightly broad sweeps; and replacing the manual-QA entry point) shortens the release cycle without over-reaching. This article covers what to hand off and what to hold back, how to design records and reproducibility, and how to keep non-determinism, cost, and sensitive-data exposure in check, based on official docs and OSS implementations.

Windows Admin-Elevated Processes Are Off-Limits to ChatGPT and Codex Computer Use — Where UIPI Draws the Line

Once you actually start using the [ChatGPT desktop app](https://chatgpt.com/download/)'s Computer Use as an AI tester on Windows, you hit a hard wall: no click or keystroke is delivered to any window belonging to an admin-elevated process. The cause is Windows' Mandatory Integrity Control (MIC) and User Interface Privilege Isolation (UIPI), which are designed to prevent a medium-integrity process from sending input to a high-integrity window at the OS level. This article walks through where that boundary sits, which tools it covers, the workarounds available in practice, and what the wall means for placing an AI tester, based on what public documentation confirms.