This computer

Local control is off by default. The Electron main process owns the bundled CUA driver lifecycle so operating-system permissions are attributed to Brainwrite rather than a background helper.

macOS

The packaged app can request Accessibility and Screen Recording permission. After granting either permission, restart the control session when prompted so macOS applies the new grant.

Ubuntu

On Linux, local control is in beta on Ubuntu 24.04 with GNOME on Xorg. In a bot's chat, open Bot's screen, find Local control and choose Enable local control (Beta). Bots you explicitly assign to This computer can then inspect the active desktop and ask for mouse or keyboard actions; every local action asks you first. Bot actions use a private cursor, so your pointer stays under your control.

On a Wayland session (other than Omarchy, below), local control stays off until its input-safety boundary is validated. Sign out and choose Ubuntu on Xorg to use This computer; Chat, Cloud desktop, Private desktop and screen preview still work on Wayland.

Omarchy (Hyprland)

On Omarchy, Hyprland's Wayland desktop, local control is experimental and needs Cua's Hyprland plugin:

1. Install and turn on cua-hyprland-plugin, as Cua's Omarchy guide describes.
2. Reload Hyprland.
3. In a bot's chat, open Bot's screen and choose Try again under Local control.

Until the plugin is on, Local control shows Plugin needed. Once it is ready, bots act through their own seat inside Hyprland, so your pointer and keyboard stay yours unless you approve a foreground action, and web pages open in the bot's own browser.

Safety model

• Enabling local control globally does not assign it to a bot.
• Choose This computer for each bot that should receive the capability.
• A bot on Ask for approval asks before each computer action; at Full access, the default, they run without a card.
• Missing permissions, unexpected binaries, unsupported desktop sessions, and failed health checks fail closed.