AI Workspace
Run supported GUI apps in RepoTunnel's isolated virtual desktop.
Guides follow the current project source. Check the release notes for your installed version.
Use AI Workspace when
The AI needs a GUI application but should not interrupt or take over your ordinary desktop session.
Session model
- Shared isolated desktop
- Per-app appSessionId
- Ownership/reclaim semantics
- Window-scoped screenshots/actions
- No implicit duplicate starts
- Other AI-owned sessions remain isolated
Choose the right control surface
AI Workspace uses an isolated desktop for AI-owned application sessions, so the human can continue working in their normal session. Normal Desktop Control is different: it targets permitted applications already running on the human desktop.
For browser-driven tasks, use RepoTunnel managed browser automation rather than starting a new Chrome process inside AI Workspace.
A reliable GUI workflow
Start or reattach to one allowed app session and inspect its windows. Observe the selected window before acting; use a semantic accessibility reference when possible, with window-relative coordinates as a grounded fallback.
After important mutations, verify the actual application state. Losing a chat session does not imply the GUI app should be closed or restarted.
- Keep a stable appSessionId for ownership
- Avoid spawning duplicate app instances
- Do not control RepoTunnel itself
- Avoid password/credential input through protected automation paths
Native platform boundaries
Linux isolates accessibility through a private AT-SPI environment. Windows UI Automation and macOS Accessibility adapters exist, but native behavior must be verified on those operating systems before making platform-specific claims.