Octo Browser Features

Octo Browser for iOS: Manage Profiles with Playwright and Puppeteer

Profiles in the Octo iOS app can now connect to Playwright or Puppeteer via CDP. The documentation explains which methods are supported and what limitations iOS introduces.

On August 28, 2026, Octo Browser announced that its iOS app supports automation through the Chrome DevTools Protocol (CDP). Mobile profiles can be connected to Playwright or Puppeteer. According to the App Store version history, CDP support was introduced in build 1.4.8 on August 21.

The app starts an HTTP server on port 9222, or on the next available port if 9222 is already in use. You can use it to retrieve the profile list, start and stop profiles, and view tabs. Each running profile has its own WebSocket address for CDP. For example, Playwright can connect to it through connectOverCDP. One address corresponds to one profile.

The documentation also lists the features that do not work on iOS. On sites with a strict CSP policy, page.evaluate and similar methods may return an EvalError; locators are recommended instead. iframe content is unavailable, request interception through page.route does not work, and browser.newContext() returns an error: here, a new context means a new profile, which must be created through the Octo API. Screenshots are returned in device pixels, with three times the resolution of CSS pixels. Text is entered through the iOS system mechanism, so input events are marked as trusted (isTrusted: true), while key presses are synthetic.

Who it is for: Users migrating existing desktop scripts to mobile profiles or running repetitive operations and tests on an iPhone. App version 1.4.8 or later is required.

Other Octo Browser news

News about other browsers

All news