app/computer-use.md Codex Docs, 2026-03-09 00:34 UTC → 2026-05-12 01:59 UTC

1# Computer Use

2 

3In the Codex app, computer use is currently available on macOS, except in the

4 European Economic Area, the United Kingdom, and Switzerland at launch. Install

5 the Computer Use plugin, then grant Screen Recording and Accessibility

6 permissions when macOS prompts you.

7 

8With computer use, Codex can see and operate graphical user interfaces on macOS.

9Use it for tasks where command-line tools or structured integrations aren't

10enough, such as checking a desktop app, using a browser, changing app settings,

11working with a data source that isn't available as a plugin, or reproducing a

12bug that only happens in a graphical user interface.

13 

14Because computer use can affect app and system state outside your project

15workspace, use it for scoped tasks and review permission prompts before

16continuing.

17 

18## Set up computer use

19 

20In Codex settings, open **Computer Use** and click **Install** to install the

21Computer Use plugin before you ask Codex to operate desktop apps. When macOS

22prompts for access, grant Screen Recording and Accessibility permissions if you

23want Codex to see and interact with the target app.

24 

25To use computer use, grant:

26 

27- **Screen Recording** permission so Codex can see the target app.

28- **Accessibility** permission so Codex can click, type, and navigate.

29 

30## When to use computer use

31 

32Choose computer use when the task depends on a graphical user interface that's

33hard to verify through files or command output alone.

34 

35Good fits include:

36 

37- Testing a macOS app, an iOS simulator flow, or another desktop app that Codex

38 is building.

39- Performing a task that requires your web browser.

40- Reproducing a bug that only appears in a graphical interface.

41- Changing app settings that require clicking through a UI.

42- Inspecting information in an app or data source that isn't available through a

43 plugin.

44- Running a scoped task in the background while you keep working elsewhere.

45- Executing a workflow that spans more than one app.

46 

47For web apps you are building locally, use the

48[in-app browser](https://developers.openai.com/codex/app/browser) first.

49 

50## Start a computer use task

51 

52Mention `@Computer` or `@AppName` in your prompt, or ask Codex to use

53computer use. Describe the exact app, window, or flow Codex should operate.

54 

55```text

56Open the app with computer use, reproduce the onboarding bug, and fix the

57smallest code path that causes it. After each change, run the same UI flow

58again.

59```

60 

61```text

62Open @Chrome and verify the checkout page still works after the latest changes.

63```

64 

65If the target app exposes a dedicated plugin or MCP server, prefer that

66structured integration for data access and repeatable operations. Choose

67computer use when Codex needs to inspect or operate the app visually.

68 

69## Permissions and approvals

70 

71The macOS system permissions for computer use are separate from app approvals in

72Codex. The macOS permissions let Codex see and operate apps. App approvals

73determine which apps you allow Codex to use. File reads, file edits, and shell

74commands still follow the sandbox and approval settings for the thread.

75 

76With computer use, Codex can see and take action only in the apps you allow.

77During a task, Codex asks for your permission before it can use an app on your

78computer. You can choose **Always allow** so Codex can use that app in the future

79without asking again. You can remove apps from the **Always allow** list in the

80**Computer Use** section of Codex settings.

81 

82<CodexScreenshot

83 alt="Codex app asking for permission to use Calculator with computer use"

84 lightSrc="/images/codex/app/computer-use-approval-light.webp"

85 darkSrc="/images/codex/app/computer-use-approval-dark.webp"

86 maxHeight="420px"

87 variant="no-wallpaper"

88/>

89 

90Codex may also ask for permission before taking sensitive or disruptive actions.

91 

92If Codex can't see or control an app, open **System Settings > Privacy &

93Security** and check **Screen Recording** and **Accessibility** for the Codex

94app.

95 

96## Safety guidance

97 

98With computer use, Codex can view screen content, take screenshots, and interact

99with windows, menus, keyboard input, and clipboard state in the target app.

100Treat visible app content, browser pages, screenshots, and files opened in the

101target app as context Codex may process while the task runs.

102 

103Keep tasks narrow and stay present for sensitive flows:

104 

105- Give Codex one clear target app or flow at a time.

106- You can stop the task or take over your computer at any time.

107- Keep sensitive apps closed unless they're required for the task.

108- Avoid tasks that require secrets unless you're present and can approve each

109 step.

110- Review app permission prompts before allowing Codex to use an app.

111- Use **Always allow** only for apps you trust Codex to use automatically in

112 future tasks.

113- Stay present for account, security, privacy, network, payment, or

114 credential-related settings.

115- Cancel the task if Codex starts interacting with the wrong window.

116 

117If Codex uses your browser, it can interact with pages where you're already

118signed in. Review website actions as if you were taking them yourself: web pages

119can contain malicious or misleading content, and sites may treat approved clicks,

120form submissions, and signed-in actions as coming from your account. To keep

121using your browser while Codex works, ask Codex to use a different browser.

122 

123The feature can't automate terminal apps or Codex itself, since automating them

124could bypass Codex security policies. It also can't authenticate as an

125administrator or approve security and privacy permission prompts on your

126computer.

127 

128File edits and shell commands still follow Codex approval and sandbox settings

129where applicable. Changes made through desktop apps may not appear in the review

130pane until they're saved to disk and tracked by the project. Your ChatGPT data

131controls apply to content processed through Codex, including screenshots taken

132by computer use.