Permission first
Desktop control is disabled until the user enables the relevant project-level permission. AI actions target enabled applications and cannot use RepoTunnel's own UI as a control surface.
- Application-scoped control
- Semantic element targeting where available
- Window-relative coordinate fallback
- Credential/password typing blocked
When to use it
Use normal Desktop Control when interaction with an already-running real desktop application is genuinely required. Use AI Workspace when the AI should work without interrupting the user's real desktop.
Ground actions in the selected application
Grant desktop permission locally, inspect the actual application state and use the available semantic or visual controls for the task.
Desktop permission is separate from project write access. RepoTunnel blocks AI control of RepoTunnel itself and does not silently widen a permission when an operation is denied.
Use the narrowest suitable surface
A build is usually a command workflow, a repository edit is usually a file workflow, and web testing is usually a managed-browser workflow. Reserve desktop actions for work that depends on a native application’s interface.
For an isolated multi-application task, use AI Workspace and verify its saved output.