Security and permissions

Two approvals. Both are yours.

Full access covers everything the computer allows now and any capability it allows later. Chosen capabilities stay limited to what you approved. Signing in alone gives no assistant access.

What each permission covers

Files

Reads use locally approved folders. Mac edits and downloads additionally need execution and local write permission. The Windows preview supports reads only.

Terminal

Requires local execution approval and an assistant grant. Commands run as your user, with file and network access beyond the folders approved for Files. A working directory is not a sandbox.

Browser

Uses a selected Chrome profile and explicitly shared tabs. Reading content and interacting with it require separate grants. The Omega Relay extension connects locally through native messaging.

Screen & control

Mac screen access needs Screen Recording and Accessibility permissions. Live view is a separate dashboard session for you to watch or take over; assistant screen actions do not consume that viewing allowance.

Agents

Requires local Agents permission, an assistant grant and a supported agent program already configured on your computer. That program runs with your user permissions and its own provider account.

Stop new access. Check running work.

Pause a computer in Computers or revoke a connection in Assistants. These block new calls; submitted commands, jobs or terminal sessions may still finish. Stop running work explicitly.

If a result is pending or unknown, ask your assistant to check the same request before retrying. A timeout does not mean nothing happened. Execution tickets expire within 60 seconds; interrupted or unknown actions must not be replayed.

Where requested data goes

Requested arguments and results pass through the device platform to your assistant. Relay activity records identifiers and status rather than file text or command output. Your assistant provider handles returned content under its own terms.