use-cases/qa-your-app-with-computer-use.md Codex Docs, 2026-03-16 18:25 UTC → 2026-05-01 18:29 UTC

1# QA your app with Computer Use | Codex use cases

2 

3Codex use cases

4 

5![](/assets/OpenAI-black-wordmark.svg)

6 

7![Codex](/assets/OAI_Codex-Lockup_Fallback_Black.svg)

8 

9Codex use case

10 

11# QA your app with Computer Use

12 

13Click through real product flows and log what breaks.

14 

15Difficulty **Intermediate**

16 

17Time horizon **30m**

18 

19Use Computer Use to exercise key flows, catch issues, and finish with a bug report.

20 

21## Best for

22 

23 - Teams validating real user flows before a release

24- QA loops that should end with severity, repro steps, and a short triage summary

25 

26# Contents

27 

28[← All use cases](https://developers.openai.com/codex/use-cases)

29 

30Copy page [Export as PDF](https://developers.openai.com/codex/use-cases/qa-your-app-with-computer-use/?export=pdf)

31 

32Use Computer Use to exercise key flows, catch issues, and finish with a bug report.

33 

34Intermediate

35 

3630m

37 

38Related links

39 

40[Computer Use](https://developers.openai.com/codex/app/computer-use) [Codex skills](https://developers.openai.com/codex/skills)

41 

42## Best for

43 

44 - Teams validating real user flows before a release

45- QA loops that should end with severity, repro steps, and a short triage summary

46 

47## Starter prompt

48 

49 @Computer Use Test my app in [environment].

50 Test these flows:

51 - [hero use case 1]

52 - [hero use case 2]

53 - [hero use case 3]

54 For every bug you find, include:

55 - repro steps

56 - expected result

57 - actual result

58 - severity

59 Keep going past non-blocking issues and end with a short triage summary.

60 

61[Open in the Codex app](codex://new?prompt=%40Computer+Use+Test+my+app+in+%5Benvironment%5D.%0A%0ATest+these+flows%3A%0A-+%5Bhero+use+case+1%5D%0A-+%5Bhero+use+case+2%5D%0A-+%5Bhero+use+case+3%5D%0A%0AFor+every+bug+you+find%2C+include%3A%0A-+repro+steps%0A-+expected+result%0A-+actual+result%0A-+severity%0A%0AKeep+going+past+non-blocking+issues+and+end+with+a+short+triage+summary. "Open in the Codex app")

62 

63 @Computer Use Test my app in [environment].

64 Test these flows:

65 - [hero use case 1]

66 - [hero use case 2]

67 - [hero use case 3]

68 For every bug you find, include:

69 - repro steps

70 - expected result

71 - actual result

72 - severity

73 Keep going past non-blocking issues and end with a short triage summary.

74 

75## Introduction

76 

77Computer Use is a strong fit for QA passes because it can see the interface, click through flows, type into fields, and record what fails. That makes it useful for catching both functional bugs and UI issues across realistic user journeys.

78 

79The key is to tell Codex what environment to test, which flows matter most, and what kind of report you want back.

80 

81## How to use

82 

831. Install the [Computer Use plugin](https://developers.openai.com/codex/app/computer-use).

842. Tell Codex which app, build, or environment to test.

853. Name the flows or hero use cases you care about most.

864. Ask for a structured report so the output is easy to triage or hand off.

87 

88You can keep this broad:

89 

90- `@Computer Use Test my app. Find any major issues and give me a report.`

91 

92Or make it more explicit:

93 

94- `@Computer Use Test my app in staging. Cover signup, invite a teammate, and upgrade billing. Log every bug with repro steps, expected result, actual result, and severity.`

95 

96If you already maintain a test-plan file in the repo, attach it to the thread or point Codex at it so the QA pass follows your existing flows.

97 

98## Practical tips

99 

100### Be explicit about setup

101 

102If account state, test data, feature flags, or environment choice affect the flow, include that up front. Codex will produce much better results when it knows whether it is testing local, staging, or production-like behavior.

103 

104### Name the issue types you care about

105 

106Call out whether you want Codex to focus on broken functionality, layout issues, confusing copy, visual regressions, or all of the above.

107 

108### Decide whether to stop or continue

109 

110If one blocking issue should end the run, say so. Otherwise, tell Codex to continue through the rest of the flow and collect all non-blocking issues before it summarizes.

111 

112## Good follow-ups

113 

114After the QA pass, keep the same thread open and ask Codex to fix one of the bugs it found, turn the findings into Linear or GitHub-ready drafts, or narrow the next pass to one specific failing flow.

115 

116## Suggested prompt

117 

118**Run a Structured QA Pass**

119 

120 @Computer Use Test my app in [environment].

121 Test these flows:

122 - [hero use case 1]

123 - [hero use case 2]

124 - [hero use case 3]

125 For every bug you find, include:

126 - repro steps

127 - expected result

128 - actual result

129 - severity

130 Keep going past non-blocking issues and end with a short triage summary.

131 

132## Related use cases

133 

134[![](/images/codex/codex-wallpaper-3.webp)

135 

136### Automate bug triage

137 

138Ask Codex to check recent alerts, issues, failed checks, logs, and chat reports, tune the...

139 

140Automation Quality](https://developers.openai.com/codex/use-cases/automation-bug-triage)[![](/images/codex/codex-wallpaper-2.webp)

141 

142### Debug in iOS simulator

143 

144Use Codex to discover the right Xcode scheme and simulator, launch the app, inspect the UI...

145 

146iOS Code](https://developers.openai.com/codex/use-cases/ios-simulator-bug-debugging)[![](/images/codex/codex-wallpaper-2.webp)

147 

148### Deploy an app or website

149 

150Use Codex with Build Web Apps and Vercel to turn a repo, screenshot, design, or rough app...

151 

152Front-end Integrations](https://developers.openai.com/codex/use-cases/deploy-app-or-website)