Computer use and system permissions
3 minute read · Settings
Computer use lets a supported agent inspect or interact with applications on your computer. Browser automation, operating-system access and a chat's action permissions are separate choices. Configure only the capabilities needed for the requested task.
Choose access in Settings
Open Settings → Computer use. App access → Manage opens system access information. Use saved app permissions reuses decisions you chose to remember; turning it off makes the next permission request ask again. Review the saved app permissions when an application should no longer be available.
Vortex browser allows agents to control website tabs with your browser sessions. Local app Preview remains available when that option is off. This is the same preference as Agent Browser Use in Browser settings; see browser profiles before sharing a signed-in page with an agent.
Check the operating system
Open Settings → System permissions and refresh the reported status. Use the offered request or system-settings action when a feature needs it. The page reports what this operating system can check; it does not promise an app-wide status for every device or network connection.
- On macOS, screen capture and app control can require Screen Recording and Accessibility permissions for the running Vortex application. Follow the system prompt and restart when the operating system requests it.
- On Windows, interactive desktop actions need an available desktop session. A locked session can prevent those actions even while background agent work continues.
- On Linux, desktop control uses the current graphical session. Wayland asks you to choose screens and allow control; window listing and focus are available on X11. Device permissions and installed desktop services can affect availability.
Microphone and camera access are needed only for features that use them. Network and USB behavior also depends on the particular device, connection and system configuration. An unavailable status is not permission to disable operating-system protections.
Give a concrete task
Name the application and outcome: “Open the local article app and verify that search finds the title I saved.” The agent should use direct Preview controls when they support the page, and desktop control for surfaces that need it. Do not enter passwords or verification codes into the conversation; enter them in the relevant secure application or system dialog.
Review any permission request in its owning chat. Saved application access does not expand the task to unrelated files or accounts. Plan remains read-only; actual approval requirements and runtime denials still apply. Stopping a run ends further work but does not reverse clicks or writes already completed.
Verify and troubleshoot
Check both the visible result and the saved outcome. A screenshot proves only what was visible at that moment. If an action fails, identify the selected app, permission state, operating system and whether the desktop is locked. Refresh the screen after a window moves before asking for another action.
For a report, share the smallest useful screenshot and sanitized error. Settings → Privacy & diagnostics provides diagnostic-file controls; review the content before sharing. See permissions and support.