Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Computer use
Bots with Use the computer on get the built-in computer MCP server (codync-host mcp computer, host/src/mcp.rs). Every agent sees the same server; the host lists its tools and runs every call (computerTools, computerCall, loopback only), so Codync's rules apply whatever the harness:
- One bot at a time. While a phone has taken over Remote screen, bots may only use tools that look.
type_logintypes a saved login only into its own site or app, and a password only into a password field. The agent never sees the value.- The harness's own approval rules still apply to each call.
Computer access setup
Desktop onboarding includes Computer access, also available from Settings → Computer access and the tray's Set up computer access… action. Users can choose Set up later and keep using chat. Setup choices stay on this installation.
The desktop setup uses a compact device header and one outlined permission group, matching the toolbar and composer outlines. Rows distinguish ready, current and waiting steps; host and setup errors appear before the checklist. This requested outline is an exception to the default borderless filled-card rule. The shared Electron layout applies to macOS, Linux and Windows. iOS and terminal retain their existing status and setup guidance: neither runs this local graphical permission onboarding, so their layout is unaffected.
- macOS: explicitly enable the background helper, then request Screen Recording and computer control. Depending on macOS, control is listed as Device Control and Data Access or Accessibility. Setup identifies the exact helper name. Codync Screen includes the Codync icon for system permission lists. A fresh installation registers the helper only when enabled; existing registrations are maintained across updates.
- Opening setup, starting the macOS helper and returning from System Settings only check grants. Native prompts require an explicit setup action through local-only
requestScreenPermission. The helper refuses to start the embedded driver until both grants are present. Newly granted screen recording triggers the existing helper restart mechanism. - Linux: setup opens the system screen-sharing portal for a display, mouse and keyboard. Helper startup never opens a chooser. The session survives host reconnections; after the helper itself restarts, reopen setup to restore sharing explicitly. Denied or partial grants can be retried.
- Windows: computer-use bots need no macOS-style grants. Setup explains that phone screen viewing is not yet supported.
- iPhone: pair through QR / Ask Access, with no SSH configuration. The viewer explains missing permissions and points to setup on the computer. Capture-only access allows viewing; takeover remains disabled until input is allowed, and revoking input exits takeover.
- Terminal UI: the bot editor shows current helper/permission status and points to Computer access. System Settings, background-service registration and portal choosers require the graphical desktop, so the terminal does not issue those prompts. Status follows host events.
Desktop setup polls read-only status while open and checks again on focus. Opening Settings never counts as a grant. Failures retain retry and Settings actions; completion requires actual platform-specific status. Skipping grants no permissions. Older clients ignore the additive permissionApp status field.
The driver
The tools come from cua-driver (MIT), which works on apps in the background: by accessibility element where it can (element_token from get_window_state), by pixels posted to the app otherwise, and in the foreground only when a call asks for delivery_mode: "foreground". The user's cursor and front app stay theirs.
host/src/screen/cua.rs owns it. One daemon serves every bot, started on first use and stopped with whoever started it (CUA_DRIVER_PARENT_LIVENESS_STDIN: its stdin closes when the parent ends, crash included). Requests use its line protocol on a private socket (Windows: a random named pipe), with the session codync-<bot>. Telemetry and update checks are off.
| Who starts the driver | Permissions | |
|---|---|---|
| macOS | Codync Screen (apps/screen-macos/Driver.swift, driver request), spawned directly with CUA_DRIVER_EMBEDDED=1 |
Codync Screen's Accessibility and Screen Recording grants: macOS attributes the child to it, so the user grants nothing new and the driver never prompts |
| Windows | The host, from beside codync-host.exe |
None; windows running as administrator are out of reach |
| Linux X11, Sway | The host, from beside codync-host (DISPLAY filled in when the service has none; Sway gets CUA_DRIVER_RS_ENABLE_WAYLAND=1) |
None |
| Linux GNOME, KDE, other Wayland | Not used: bots get Codync Screen's portal tools instead (helper_tools.rs: screenshot, click, type… on screenshot pixels) |
The Remote screen portal grant |
On macOS, windows on another Space have no accessibility tree, so background actions there are refused; the driver says so and suggests delivery_mode: "foreground".
Computer use needs Remote screen on where Codync Screen takes part (macOS, Linux); on Windows it is always available. The host's screen state says which (computerUse), and the bot editor's toggle explains it.
Tools
The host offers 16 driver tools (packaging/cua-driver/tools.mjs lists them): list_apps, list_windows, get_window_state, get_desktop_state, zoom, launch_app, click, double_click, right_click, drag, scroll, type_text, press_key, hotkey, set_value, invoke_menu, plus type_login (not on Windows yet). Left out: bring_to_front and kill_app (they take over or end the user's apps), clipboard_read, the browser_* tools (each browser asks for Automation separately), and the driver's configuration, recording and session tools.
Descriptions come from the running driver, so they match the platform; when it can't start, the host lists the copy in host/src/screen/cua_tools.json and each call explains why it failed. Results pass through as MCP content. When the text is only a summary, the structured data follows as JSON; window snapshots add how to spell element tokens (<snapshot_id>:<index>).
type_login {login, field, pid?}: Codync Screen reads the focused control of that app (focusedField: app, page URL, secure field), the host checks it against the login, then types through the driver into that app in the background (macOS) or into the checked active window (Linux). The driver's reply is not passed on.
Packaging
packaging/cua-driver/driver.json pins the release and the SHA-256 of each archive; fetch.mjs <target> <dir> downloads, checks and copies the executables with cua-driver.LICENSE:
- macOS: the
Screentarget's Embed cua-driver build phase puts it inCodyncScreen.app/Contents/Helpers/. electron-builder leaves its Developer ID signature alone (mac.signIgnore). - Windows:
tools/native-host.mjsputscua-driver.exeandcua-driver-uia.exenext to the host inresources/. - Linux: the host release archive carries
cua-driver(needs libX11, libXi and libxkbcommon);install.sh, Homebrew andcodync-host updateput it next to the host.
Updating the driver: change driver.json (version, tag, assets and sums from the release's SHA256SUMS), run node packaging/cua-driver/tools.mjs <path to the new cua-driver>, check the tool list diff, and run the checks below.
Verification
- Host:
cargo testcovers the tool list, result shaping, the line protocol and takeover. - macOS: with a fresh build, ask a computer-use bot to read a background app's window and click a control in it. The front app must not change and macOS must not ask for any new permission. Take over from the phone mid-task: actions stop, looking still works.
- Windows and Linux X11: the same task; Linux GNOME still gets the portal tools.
type_logininto a test site's password field, and a refusal for the wrong site or a non-password field.