Desktop, web, and mobile

Local projects

The studio requires an account and an internet connection. Local projects use the same studio with a folder on your machine: source files and engine execution stay on that machine, while project metadata, tasks, settings and Design state use hosted services. Local does not mean fully offline or that all project data stays on the device.

Cloud projects

Free includes unlimited local projects and one active collaborative cloud project. Project collaboration and publishing a saved target for review are explicit actions. Project membership and review links do not grant access to another person’s machine. Opening Design does not automatically synchronize the source folder.

Machine-backed work

Working-tree edits, installed Build engines, git credentials, gates, package scripts, local preview, terminal, folder binding, and machine-local design-system extraction require a Mac. The machine is the trust boundary; source and vendor CLI credentials do not move into Iterel Cloud.

Connected browser

On supported Mac builds, open App settings → Connections → Browser to enable browser access and check the connection. If setup is missing, Iterel tracks it as a setup task. The Iterel extension for Chrome connects the browser you already use and are signed in to.

After you grant browser access, a supported run can work with the connected browser. Use + → Use a browser tab or Use this tab in Iterel in Chrome to identify the tab you mean. Attaching a tab only adds context; it never sends your prompt. It is a target shortcut, not a requirement to re-authorize each tab.

Browser activity appears in the run. Pictures stay on the Mac, and Chrome shows its debugging banner while a tab is controlled. Turn access off in Browser settings or from Iterel’s Chrome button to revoke it. This tool does not operate through RemoteBridge and is separate from task Preview and loopback verification.

Computer use

On supported Mac builds, App settings → Privacy → Permissions holds computer-use consent. The run’s Computer use switch additionally requires Screen Recording and Accessibility. Iterel asks before granting access to each app.

When a run acts in an allowed app, you see the pointer move and an activity overlay. Press Esc to stop immediately. Read-only rounds cannot send input. Browsers use the connected-browser tool instead; terminals and code editors do not accept typed input through computer use, and Iterel cannot control its own approval windows.

Computer use is absent on Windows, web, phone and remote rounds. Window captures are a separate way to attach visual context; attaching a capture does not grant app control.

Remote session

With a plan that includes remote control and your signed-in Mac online, web and mobile can drive it through a same-user RemoteBridge: start a round, steer supported engines, run gates, review, Accept or Discard, and create a pull request. Project membership never grants authority over another member's machine.

Mobile

Mobile is the same responsive, installable renderer—not a React Native fork or /m/ tree. A phone is a companion, not a smaller Iterel: projects, tasks, and continuing a task, plus notifications, comments, Command center, Chats, and Assets.

The making and orientation surfaces—Design, Whiteboard, Project Map, Architecture, and Ideation—are absent on a phone, not degraded. No entry point renders, and a deep link to one resolves to that project's tasks. Local projects, terminal, folder binding, local preview, and machine settings stay unavailable.

Honest degradation

If machine-backed work has no local or remote host, the composer says host offline or offers the Mac app. It never silently queues code work or swaps in a managed model without a working tree.