Skip to Content

Releases

turno 0.4.0

Several agents in one browser, flows you record once and replay, a browser you can drive from the shell, and a view to watch the agent and take over.

View source
Released

turno 0.4.0 is about the browser again. One browser identity can now serve several agents at once, each in its own tabs. What an agent does can be saved as a flow and replayed, coding agents can drive the browser from the shell, and you can watch the agent's tab and take over when a site needs a person. Two engines join Chrome: Lightpanda for reading pages with little memory, and your own Chrome. Every new setting is off until you turn it on.

Upgrade

One command

turno upgrade

Updates turno with the tool that installed it (npm, pnpm, yarn, bun, Volta, Homebrew or a git checkout), then rewrites the launchers.

Or with your package manager

npm install --global turno-cli@latest

Then run turno upgrade --finish: it rewrites the launchers, checks the config and shows what changed.

Highlights

Browser

Several agents, one browser

Until now an identity served one agent session at a time. With "sharing": "tabs" several sessions use the same signed-in browser, each with its own current tab and the tabs it holds. Another session's call on a held tab waits up to 10 seconds and then fails with a message that names the holder, browser_close closes only the calling session's tabs, and a session lets go of its tabs when it ends or after 5 minutes without a call.

turno browser set school --sharing tabs
turno browser set school \
  --tab-lock-wait 30s --tab-lock-release 10m

Serve the identity with exclusive = false in mcp.toml; turno browser doctor warns when the two disagree.

How it works

Browser

Record a flow once, replay it

browser_record saves what an agent does as a named flow. Each element is kept four ways (Playwright's locator, role and name, text and CSS path), so a small change on the page does not break it, and typed text becomes parameters. Passwords, one-time codes and values marked sensitive are never saved. browser_replay runs the flow, and when a step no longer fits it stops with a report the agent can continue from.

# saved flows and their parameters
turno browser flows school
turno browser replay school sign-in \
  --param password=keychain:school-password
# record every session, with traces
turno browser record school --flows --traces
Flows: record and replay

Browser

Drive the browser from the shell

Some coding agents prefer commands to MCP tools. turno browser do runs one browser action per command through mcpd, with the same tab locks, vault, recordings and refusals an agent gets over MCP. The commands one agent or one shell runs share a session and keep their tab until end. The Claude Code plugin adds a short browser-identity skill that teaches the loop.

turno browser do school open \
  https://mail.example.com/
turno browser do school snapshot   # refs like e12
turno browser do school click e12
turno browser do school end
From the shell

Browser

Watch the agent and take over

Off by default. With --live true turno-browser serves a view of the agent's tab on 127.0.0.1, behind a link that works once and is never printed. Pause the agent, solve what needs a person (a sign-in, a confirmation), and resume: each held call is told what changed, and a call that would act on a stale page gets a fresh snapshot instead. A page that holds a vault value or a password is never shown.

turno browser set school --live true
turno browser live school    # opens the view
turno browser pause school   # holds the next call
turno browser resume school
Live view and take-over

Browser

Two more engines

Read mode runs an identity on Lightpanda instead of Chrome, to read pages with a fraction of the memory; tools that need a laid-out page are refused with the reason. Attach mode connects to the Chrome you already have open, works in a tab of its own and never closes yours. turno never downloads either engine, and turno browser doctor checks both.

# read mode
turno browser set research --engine lightpanda
# your own Chrome, with remote debugging on
turno browser set school --attach auto
Engines

Off by default

These settings exist for the cases where a site needs them. Each one is off until you turn it on per identity, and each has its own section with what it costs.

  • Human-like input: --humanize light|full|adaptive moves the pointer along a curve, holds the button and types key by key. Tool names and results do not change.
  • Natural language actions: --act adds browser_act, browser_extract and browser_observe, which run on your client's model through MCP sampling or on a chat completions API you name. The model sees a snapshot with vault values and password fields hidden, and can only use the stock actions on the current tab, every step shown.
  • Captcha solving: --captcha-provider sends a reCAPTCHA, hCaptcha or Turnstile widget to a solver service you name. The service sees the page, and solving a site's captchas by machine may break its terms: it is for your own accounts.
  • Network and user agent: a coherent user agent for headless Chrome, checked against its client hints, headers, languages and time zone at launch, and a proxy per identity with its password only in the secret store.
  • Camoufox: runs an identity on an installed Camoufox through stock Playwright, with its own Firefox profile.

Keys for these services are only keychain: references, read from the secret store when used and hidden from every result. See Acceptable use.

Browser

  • Faster errors: when another element covers the target of a click, and still covers it 300 ms later, the error names that element at once instead of after the 5 second timeout.
  • No more closed-page errors: a tool call waits for the tab governor to finish closing a popup or a parked tab.
  • Cleanup: a server in read mode stops a Lightpanda that a killed server left running, and turno browser doctor --fix does too.
  • Benchmarks: an evaluation suite of browser tasks with paired runs, and a fingerprint and event bench that shows what a page can observe about the browser.

CLI

  • Faster status: turno doctor, turno status and turno mcp daemon status no longer wait for lsof to tell who holds mcpd's port, which took seconds on a busy Mac.
  • turno browser <id> <action>: the short form of turno browser do, when the id is not a subcommand.

Changed behavior

What can change when you upgrade from 0.3:

  • Third-party storage partitioning: Chrome now keeps it on, as a person's Chrome does. Playwright turns it off, and turno used to as well, so a site embedded in another one now sees storage of its own there.

On this page