Skip to content

Releases

turno-fonts 0.1.2

Choose a tag to compare

@github-actions github-actions released this 19 Nov 00:38
275d91b

What's new in turno 0.3.0: https://turno.wimo.dev/docs/releases/v0-3-0

Patch Changes

  • 2948759: The package homepage is now https://turno.wimo.dev.
  • 5566437: Every package has a README that tells the same story as the site. turno-cli's follows the
    order of turno.wimo.dev and lists what the browser gained; turno-browser's is organized around
    what the package does (identities, the credential vault, session export and import, tab limits,
    browser_batch, blocking and cache, health and doctor); turno-core's says what the shared
    package is for; turno-fonts' shows the status line and how turno ui install uses the font.
    Each links to its page on turno.wimo.dev and to the releases.

A CycloneDX SBOM is attached.

turno-core 0.1.0

Choose a tag to compare

@william-monroy william-monroy released this 19 Nov 00:39
f33bfa3

What's new in turno 0.3.0: https://turno.wimo.dev/docs/releases/v0-3-0

Minor Changes

  • a0bfce8: New package turno-core with what turno-cli and turno-browser share: turno's paths, the secret
    store (macOS Keychain, Linux Secret Service) and the process helpers. Both packages
    now depend on it instead of keeping their own copies; behavior is unchanged.

Patch Changes

  • 2948759: The package homepage is now https://turno.wimo.dev.
  • 5566437: Every package has a README that tells the same story as the site. turno-cli's follows the
    order of turno.wimo.dev and lists what the browser gained; turno-browser's is organized around
    what the package does (identities, the credential vault, session export and import, tab limits,
    browser_batch, blocking and cache, health and doctor); turno-core's says what the shared
    package is for; turno-fonts' shows the status line and how turno ui install uses the font.
    Each links to its page on turno.wimo.dev and to the releases.

Published by hand as the first version of the package, without provenance; later versions come from release.yml with provenance.

turno-cli 0.4.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 14:17
e1267a5

What's new in turno 0.4.0: https://turno.wimo.dev/docs/releases/v0-4-0

Minor Changes

  • 50facc9: Record and replay. browser_record saves an agent's actions on an identity as a named flow, each
    element kept four ways (Playwright's locator, role and name, text, CSS path) and typed text as
    parameters; passwords, one-time codes and values marked sensitive are never saved, and a vault
    sign-in is kept as browser_login with the site name. browser_replay runs a flow with
    parameters (keychain:<item> reads one from the secret store) and, when a step no longer fits,
    stops with a report the agent can continue from; browser_flows lists them. Opt-in per identity
    (record in identity.json, turno browser record <id>): every session as a flow, Playwright
    traces and a screenshot per action under a size cap, with the trace stopped around sign-ins.
    New commands turno browser flows|replay|record|traces; traces --open uses the trace viewer
    bundled with patchright-core.
    With "sharing": "tabs" a recording holds only the session that started it and replay runs in
    that session's tabs; traces and screenshots are refused in attach mode and in read mode.

  • e94a153: Natural language actions and captcha solving for browser identities, both not recommended and off by default.

    • turno identity set browser:<id> --act lists browser_act (an instruction carried out one stock browser action at a time, every step shown), browser_extract (data off the page as JSON) and browser_observe (proposed calls, not run). The model is your client's, through MCP sampling, or a chat completions API you name with --act-provider chat-completions --act-endpoint <url> --act-model <name> --act-key keychain:<item>. The model sees the instruction and a snapshot of the current tab with vault values and password, one-time code and card fields hidden; it can only click, type, select, press keys, hover, drag, wait and go back on that tab; steps, tokens and time are capped per call (--act-max-steps, --act-max-tokens, --act-timeout). A recorded flow keeps the stock steps it chose, never the instruction or the page.
    • --captcha-provider task-api --captcha-endpoint <url> --captcha-key keychain:<item> lists browser_solve_captcha, which sends a reCAPTCHA v2, hCaptcha or Turnstile widget and the page address to that solver service and puts the token into the page. The service sees the page, and solving a site's captchas by machine may break its terms: it is meant for your own accounts. Every attempt is a line in the identity's reputation log, and turno browser reputation shows a solved column once a solver answered. Read mode refuses it.
    • Keys are only keychain: references read from the secret store at use time, refused as literal values without being echoed, and hidden from every result.
    • identity.json format 8 (act, captcha); turno-browser API 1.7, which turno-cli now requires.
  • dcc2b97: Two opt-in engines for browser identities and servers, both off by default.

    Read mode runs an identity (or one server) on Lightpanda instead of Chrome, for reading pages
    with a fraction of the memory: turno browser set <id> --engine lightpanda, or
    turno-browser-mcp --engine lightpanda. turno never downloads Lightpanda; it runs the
    lightpanda on your PATH (or at TURNO_LIGHTPANDA_PATH), on a private Unix socket with
    Lightpanda's telemetry off. The tools that work there run; the others (screenshots, dialogs,
    drag and drop, uploads, browser_login) are refused with the reason before they reach the
    browser. An identity in read mode keeps its own cookie jar, apart from its Chrome profile.

    Attach mode connects to the Chrome you already have open, so the agent works in your signed-in
    browser: turno browser set <id> --attach auto (after you turn on remote debugging at
    chrome://inspect/#remote-debugging, Chrome 144 or newer), a Chrome user data folder, or a
    loopback endpoint; turno-browser-mcp --attach <target> for one server. Chrome asks you to allow
    each connection. turno works in a tab of its own, closes only the tabs it opened (on
    browser_close, at the end of the session and at the idle limit) and never closes Chrome; the
    tab governor leaves your tabs alone, and browser_run_code_unsafe is refused.

    turno browser doctor gains an Engines section (Lightpanda found or how to install it, a
    Lightpanda left running, which --fix stops) and checks each identity's attach target without
    connecting. identity.json is now format 6 (engine, attach), and the turno-browser API is 1.5.

    Read mode works with "sharing": "tabs". Two pairs are refused with the reason, in identity.json
    and from server flags: attach mode with "sharing": "tabs" (turno keeps one agent's tabs apart
    from yours in your Chrome, not several sessions apart), and read mode with humanize (Lightpanda
    lays out no page, so there is no pointer path to play). Attach mode works with humanize.

  • 4814fb8: Human-like input for browser identities, off by default. turno identity set browser:<id> --humanize light|full|adaptive (or turno-browser-mcp --humanize <level>, which wins) makes the stock click, hover, type, fill form, select, drag, press key and coordinate tools, and browser_batch, move the pointer along a curve from where it last was to a point inside the target, hold the button for tens of milliseconds and type short text key by key with per-key delays. full adds a move time that follows distance and target size, overshoot and correction, a reading pause on a new page, longer gaps between words and wheel scrolling; adaptive is light, and full on a site where the identity met a challenge page. Tool names, arguments and results do not change. The setting is the humanize key of identity.json (format 4, with an optional seed), and turno-cli needs turno-browser API 1.3 for it.

  • bf1cafb: turno browser do <id> <action> drives a browser identity from the shell, for coding agents that
    prefer commands to MCP tools: open, back, snapshot, read, find, click, type,
    press, select, hover, wait, screenshot, tabs, login (a vault sign-in), call (any
    tool of the server), close, session and end. Each action is one tool call through mcpd to the
    identity's turno-browser-mcp, so the tab locks or the one-session lease, attach mode, read mode's
    refusals, humanize, recordings and the vault apply as they do to an agent. The commands one agent
    or one terminal shell runs are one session and keep their tab: turno keeps the mcpd session open
    between them and ties it to the agent (or the shell), and end closes it; --session <name> or
    TURNO_BROWSER_SESSION keeps several apart. Output is url: and title: lines and what the
    action returned, errors on stderr with exit 1, or one object with --json. turno browser <id> <action> is the short form when the id is not a subcommand. The Claude Code plugin adds a short
    browser-identity skill that teaches the loop and reads the installed help first.

  • 6698608: Live view and take-over for browser identities, off by default. turno browser set <id> --live true (or turno-browser-mcp --live) serves a view of the agent's tab on 127.0.0.1 with a per-server token; turno browser live <id> opens it through a link that works once and is never printed. turno browser pause <id> (or Pause in the view) holds the agent's next call, up to live.wait (2 minutes by default), while you act in the window or through the view; turno browser resume <id> lets it go, and each held call is told what changed (URL, title, tabs, your input) and a call that would act on stale refs is not run: it returns an error with a fresh snapshot. The natural language and captcha tools are held too, and a browser_act run stops at its next step. A page that holds a vault value or a password is never shown, including a sign-in typed key by key with humanize. Read mode and attach mode refuse the view and keep pause and resume. turno-browser API 1.9, identity.json format 10.

  • c716051: Opt-in network and user agent settings, and a Camoufox engine, all off by default and not
    recommended for your own accounts. identity.json format 11 adds userAgent and proxy, and the
    engine key takes "camoufox" (also format 11); API_VERSION is 1.10 and turno-cli needs it.
    "userAgent": "coherent" takes no typed value: a headless Chrome gets the user agent a headed one
    of the same version sends, with its real client hints metadata, and a launch check refuses any
    contradiction between the user agent, client hints, platform, headers, languages and time zone.
    proxy sends the identity's traffic (sign-ins included) through an http, https or SOCKS proxy,
    with its password only from the secret store, hidden from every tool result, and WebRTC limited
    to the proxy. --engine camoufox runs an identity on an installed Camoufox through stock
    playwright-core, with its own Firefox profile; turno never downloads it, and every stock tool but
    browser_run_code_unsafe runs, as do natural language actions, browser_login and
    turno browser do. Captcha solving is refused with it, and the live view shows no picture there
    (pause and resume work). The act model's prompt and the live view's tab list hide the proxy
    credentials. New flags on turno identity set (--user-agent,
    --proxy-server, --proxy-username, --proxy-password, --no-proxy), doctor checks for
    Camoufox and the proxy credentials, and fingerprint bench checks that compare headers and a
    worker with the page.

  • 4b9556f: Several agent sessions can now share one browser identity, each in its own tabs. Turn it on per identity with "sharing": "tabs" in identity.json (turno identity set browser:<id> --sharing tabs, or the server's --sharing tabs) and serve the identity with exclusive = false in mcp.toml; the default stays one session at a t...

Read more

turno-cli 0.3.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 00:38
275d91b

What's new in turno 0.3.0: https://turno.wimo.dev/docs/releases/v0-3-0

Minor Changes

  • cc6b5b2: Browser identity module:

    • identity.json next to each identity's profile keeps its time zone, languages, locale and
      region fixed; Chrome gets them at every start (--accept-lang, --lang, and the time zone
      when it differs from the machine's). turno identity add browser:<id> pins a new identity to
      the current time zone and takes --timezone, --locale, --languages, --region and a
      health check; turno identity show and turno identity set read and change it
      (turno browser show/set <id> too). Without the file nothing changes.
    • A runtime lock ({ nodePid, chromePid, pgid, startedAt }) while an identity's Chrome runs: a
      second session gets a message naming the process and how to stop it instead of "Browser is
      already in use".
    • An optional session health check (a URL and a text or selector) marks a signed-out identity
      NEEDS_AUTH; tool calls then fail with a message that asks for turno browser login <id>.
    • Each captcha, "verify it's you" or block page an identity meets is logged per site (host name
      only); turno browser reputation [<id>] [--json] shows counts and trend.
    • turno browser doctor [--fix] [--no-launch] [--json]: Chrome and its version, a smoke launch,
      the desktop session, and per identity its settings, lock, sign-in and recent challenges, with
      a fix for each problem.
    • mcpd: stop_grace per server in mcp.toml, the wait between closing stdin and SIGTERM;
      5 seconds by default for turno-browser-mcp, the SDK's 2 seconds for every other server.
  • 59309b5: turno browser export <id> --out <file> and turno browser import <file> [--as <id>] move an
    identity's cookies, localStorage and IndexedDB as one file encrypted with a passphrase (scrypt
    and AES-256-GCM), refused after its expiry and never holding vault credentials.
    "keychain": "system" in identity.json makes Chrome encrypt an identity's cookies with the OS
    keychain instead of Playwright's fixed mock key; the default is unchanged.
    turno-browser's API is now 1.2, which this turno requires.

  • 50dd77c: Credential vault for browser identities: turno browser vault add|list|remove|submit
    stores a username, a password and an optional TOTP secret per site in the OS secret store, and
    the new browser_login tool fills them into the site's sign-in page without the agent ever
    seeing them. Results and errors are redacted, values are bound to the site's origins, and the
    form is submitted only when the identity opts in. turno-browser's API is now 1.1, which this
    turno requires.

  • aa7e39e: An output contract for scripts, hooks and agents:

    • Every --json object carries schemaVersion (each element, for a list); no existing key
      changed. --json=fields lists a command's fields, --json=a,b keeps only those, and an
      unknown field is exit 2 with the list. Under --json, errors are one JSON line on stderr:
      {"schemaVersion":1,"error":{"code":"usage","exitCode":2,"message":"..."}}.
    • turno limit show --watch --json and the new turno mcp top --watch --json print NDJSON, one
      record per line, like turno mcp log --follow --json.
    • Exit codes: 0 ok, 1 failure, 2 usage, 3 no profile for the folder, 4 not signed in, 5 mcpd
      down (turno help exit-codes). Changed: turno auto exits 3 (was 1) when the folder's
      profile does not exist or there is no rule with system = ""; turno mcp daemon status,
      turno mcp top and turno mcp savings exit 5 (was 1) when mcpd is down.
    • turno profile which --check answers with that code and prints nothing when the folder has
      a signed-in profile (--agent for other agents).
    • turno's own state files are checked before use: a cut or hand-edited file reads as absent
      instead of crashing, and an unreadable mcp-managed.json stops turno mcp sync and
      turno uninstall with a message naming the file (they used to go on as if it were empty).
      turno identity log --verify reports a line that is not an audit entry.
    • turno help environment lists every variable turno reads and turno help json the JSON
      rules; every command help ends with examples. Colors honor CLICOLOR=0, CLICOLOR_FORCE
      and TERM=dumb; TURNO_NO_UPDATE_NOTIFIER=1 turns the update check off.
  • fa324c0: Cross-package contracts:

    • turno-browser exports its public API as a typed api object with API_VERSION (1.0).
      turno-cli checks it when it loads the package: a turno-browser that is too old (0.2 and older
      have no API_VERSION) or too new stops turno browser and turno identity browser:<id>
      with one line naming what to update, instead of failing later.
    • mcpd sends every tools/call, from 2025-11-25 sessions and 2026-07-28 requests alike,
      through one call middleware: the profile's tool filter, then the call log, then the session id.
      Refusals and call log records are unchanged.
    • Each relayed tools/call carries _meta["io.turno/session"], an opaque id that is stable for
      one agent session and different for every other. turno-browser-mcp hands it to its own tools
      (session in their context); the Playwright tools are unaffected.
  • cf4e077: Diagnostics and safe mode:

    • turno mcp call <server> [tool] [--args JSON] [--arg k=v|k:=json] [--profile p] [--json]
      calls a tool through mcpd as a profile's session in this folder would, or lists the tools.
      Exits 1 on isError or a refused call, 5 when mcpd is down.
    • turno doctor --report prints a Markdown block for an issue: turno, Node, OS, each agent's
      version, mcpd, the findings and every path, with no tokens or secret values.
      turno config path --all lists every path turno uses.
    • Safe mode: turno run <p> --no-gateway, turno <p> --no-gateway, turno auto --no-gateway,
      or TURNO_SAFE=1, opens the agent with the profile's account but without the gateway entries,
      the gateway token and (Claude Code) the status line and hooks.
    • Copilot CLI and Cursor CLI gateway entries send the session folder (X-Turno-Cwd-B64), so
      folder server sets apply to them without the process lookup. Run turno mcp sync to rewrite
      existing entries.
    • system = "" no longer becomes an empty profile name for the hub's gateway token; turno status and turno profile which say "no profile" for folders without a rule.
  • 5b46749: Browser lifecycle:

    • turno-browser-mcp passes a generated Playwright MCP --config that closes Chrome after 15
      minutes without a tool call, headed too; the next call opens it again with the same profile.
      TURNO_BROWSER_IDLE changes the limit ("10m", "0" keeps Chrome open); --idle-timeout
      and a --config of your own still win. Flags and tool names are unchanged.
    • On start it closes a Chrome that an earlier, killed run left open on the same profile (only
      a Chrome browser process for exactly that profile whose parent is gone), and on stdin close,
      SIGTERM or SIGHUP it closes Chrome within about 2.5 seconds, forcefully if needed.
    • mcpd stops a quiet session server under critical memory pressure even while its session
      lives; the next call starts it again. turno mcp top counts the process groups a server's
      children lead, so a browser's helpers always count.
    • Docs: one recommendation for browsers, a shared server with exclusive = true per identity
      (the block turno identity add prints), instead of scope = "session".
  • 57641d4: turno identity set browser:<id> and turno browser set <id> take flags for every identity.json
    key of the browser host: --tabs-max, --tabs-popups, --tabs-park, --tabs-close and
    --no-tabs (tab governor), --background-throttling, --settle, --block-trackers,
    --block-types, --block-patterns and --no-block, --cache, --cache-max-size and
    --no-cache. A flag changes only its part of a group, an empty value removes a key, and a bad
    value is refused with the flag's name. set takes --json (what changed, or with --dry-run
    what would, and the resulting file), and --dry-run now validates like the real write.
    turno identity add browser:<id> takes the same flags, and show lists the new settings.

  • 4663312: Move MCP servers between machines, OAuth detection, Codex trust and next-step hints:

    • turno mcp export [--profile p] [--json] prints mcp.toml without secret values: references
      stay, literal secrets become keychain:turno/<server>/<key> names, and the top of the file
      lists the turno secret set commands the other machine needs.
    • turno mcp import <file> merges an export, a JSON file with mcpServers or a Codex
      config.toml into mcp.toml, keeping its comments and existing servers (--force replaces
      them). A preview until --write.
    • With --write, both import forms mark remote servers that answer with an OAuth challenge as
      auth = "oauth".
    • turno profile assign and turno profile repair write Codex [projects."<folder>"] trust_level = "trusted" entries in Codex profiles for their folder rules, never changing an
      existing entry.
    • Commands that write end with a Next: line (profile add, profile assign, mcp import --write, mcp export, secret set); turno config set hints false turns them off.

Patch Changes

  • 2948759: The package homepage is now https://turno.wimo.dev.
  • 7b77664: pnpm, bun and yarn are first-class install paths. turno upgrade and turno version recognize
    them from their lockfile even under a custom PNPM_HOME, BUN_INSTALL or yarn global folder,
    and treat pnpm dlx and bunx like npx: a one-off copy has nothing to upgrade, and
    turno upgrade says which command runs the newest release instead of installing turno globally.
    Launchers and the status line refuse to point into any of those caches. turno browser and
    `t...
Read more

turno-browser 0.4.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 14:17
e1267a5

What's new in turno 0.4.0: https://turno.wimo.dev/docs/releases/v0-4-0

Minor Changes

  • 50facc9: Record and replay. browser_record saves an agent's actions on an identity as a named flow, each
    element kept four ways (Playwright's locator, role and name, text, CSS path) and typed text as
    parameters; passwords, one-time codes and values marked sensitive are never saved, and a vault
    sign-in is kept as browser_login with the site name. browser_replay runs a flow with
    parameters (keychain:<item> reads one from the secret store) and, when a step no longer fits,
    stops with a report the agent can continue from; browser_flows lists them. Opt-in per identity
    (record in identity.json, turno browser record <id>): every session as a flow, Playwright
    traces and a screenshot per action under a size cap, with the trace stopped around sign-ins.
    New commands turno browser flows|replay|record|traces; traces --open uses the trace viewer
    bundled with patchright-core.
    With "sharing": "tabs" a recording holds only the session that started it and replay runs in
    that session's tabs; traces and screenshots are refused in attach mode and in read mode.

  • e94a153: Natural language actions and captcha solving for browser identities, both not recommended and off by default.

    • turno identity set browser:<id> --act lists browser_act (an instruction carried out one stock browser action at a time, every step shown), browser_extract (data off the page as JSON) and browser_observe (proposed calls, not run). The model is your client's, through MCP sampling, or a chat completions API you name with --act-provider chat-completions --act-endpoint <url> --act-model <name> --act-key keychain:<item>. The model sees the instruction and a snapshot of the current tab with vault values and password, one-time code and card fields hidden; it can only click, type, select, press keys, hover, drag, wait and go back on that tab; steps, tokens and time are capped per call (--act-max-steps, --act-max-tokens, --act-timeout). A recorded flow keeps the stock steps it chose, never the instruction or the page.
    • --captcha-provider task-api --captcha-endpoint <url> --captcha-key keychain:<item> lists browser_solve_captcha, which sends a reCAPTCHA v2, hCaptcha or Turnstile widget and the page address to that solver service and puts the token into the page. The service sees the page, and solving a site's captchas by machine may break its terms: it is meant for your own accounts. Every attempt is a line in the identity's reputation log, and turno browser reputation shows a solved column once a solver answered. Read mode refuses it.
    • Keys are only keychain: references read from the secret store at use time, refused as literal values without being echoed, and hidden from every result.
    • identity.json format 8 (act, captcha); turno-browser API 1.7, which turno-cli now requires.
  • dcc2b97: Two opt-in engines for browser identities and servers, both off by default.

    Read mode runs an identity (or one server) on Lightpanda instead of Chrome, for reading pages
    with a fraction of the memory: turno browser set <id> --engine lightpanda, or
    turno-browser-mcp --engine lightpanda. turno never downloads Lightpanda; it runs the
    lightpanda on your PATH (or at TURNO_LIGHTPANDA_PATH), on a private Unix socket with
    Lightpanda's telemetry off. The tools that work there run; the others (screenshots, dialogs,
    drag and drop, uploads, browser_login) are refused with the reason before they reach the
    browser. An identity in read mode keeps its own cookie jar, apart from its Chrome profile.

    Attach mode connects to the Chrome you already have open, so the agent works in your signed-in
    browser: turno browser set <id> --attach auto (after you turn on remote debugging at
    chrome://inspect/#remote-debugging, Chrome 144 or newer), a Chrome user data folder, or a
    loopback endpoint; turno-browser-mcp --attach <target> for one server. Chrome asks you to allow
    each connection. turno works in a tab of its own, closes only the tabs it opened (on
    browser_close, at the end of the session and at the idle limit) and never closes Chrome; the
    tab governor leaves your tabs alone, and browser_run_code_unsafe is refused.

    turno browser doctor gains an Engines section (Lightpanda found or how to install it, a
    Lightpanda left running, which --fix stops) and checks each identity's attach target without
    connecting. identity.json is now format 6 (engine, attach), and the turno-browser API is 1.5.

    Read mode works with "sharing": "tabs". Two pairs are refused with the reason, in identity.json
    and from server flags: attach mode with "sharing": "tabs" (turno keeps one agent's tabs apart
    from yours in your Chrome, not several sessions apart), and read mode with humanize (Lightpanda
    lays out no page, so there is no pointer path to play). Attach mode works with humanize.

  • 4814fb8: Human-like input for browser identities, off by default. turno identity set browser:<id> --humanize light|full|adaptive (or turno-browser-mcp --humanize <level>, which wins) makes the stock click, hover, type, fill form, select, drag, press key and coordinate tools, and browser_batch, move the pointer along a curve from where it last was to a point inside the target, hold the button for tens of milliseconds and type short text key by key with per-key delays. full adds a move time that follows distance and target size, overshoot and correction, a reading pause on a new page, longer gaps between words and wheel scrolling; adaptive is light, and full on a site where the identity met a challenge page. Tool names, arguments and results do not change. The setting is the humanize key of identity.json (format 4, with an optional seed), and turno-cli needs turno-browser API 1.3 for it.

  • 6698608: Live view and take-over for browser identities, off by default. turno browser set <id> --live true (or turno-browser-mcp --live) serves a view of the agent's tab on 127.0.0.1 with a per-server token; turno browser live <id> opens it through a link that works once and is never printed. turno browser pause <id> (or Pause in the view) holds the agent's next call, up to live.wait (2 minutes by default), while you act in the window or through the view; turno browser resume <id> lets it go, and each held call is told what changed (URL, title, tabs, your input) and a call that would act on stale refs is not run: it returns an error with a fresh snapshot. The natural language and captcha tools are held too, and a browser_act run stops at its next step. A page that holds a vault value or a password is never shown, including a sign-in typed key by key with humanize. Read mode and attach mode refuse the view and keep pause and resume. turno-browser API 1.9, identity.json format 10.

  • c716051: Opt-in network and user agent settings, and a Camoufox engine, all off by default and not
    recommended for your own accounts. identity.json format 11 adds userAgent and proxy, and the
    engine key takes "camoufox" (also format 11); API_VERSION is 1.10 and turno-cli needs it.
    "userAgent": "coherent" takes no typed value: a headless Chrome gets the user agent a headed one
    of the same version sends, with its real client hints metadata, and a launch check refuses any
    contradiction between the user agent, client hints, platform, headers, languages and time zone.
    proxy sends the identity's traffic (sign-ins included) through an http, https or SOCKS proxy,
    with its password only from the secret store, hidden from every tool result, and WebRTC limited
    to the proxy. --engine camoufox runs an identity on an installed Camoufox through stock
    playwright-core, with its own Firefox profile; turno never downloads it, and every stock tool but
    browser_run_code_unsafe runs, as do natural language actions, browser_login and
    turno browser do. Captcha solving is refused with it, and the live view shows no picture there
    (pause and resume work). The act model's prompt and the live view's tab list hide the proxy
    credentials. New flags on turno identity set (--user-agent,
    --proxy-server, --proxy-username, --proxy-password, --no-proxy), doctor checks for
    Camoufox and the proxy credentials, and fingerprint bench checks that compare headers and a
    worker with the page.

  • 4b9556f: Several agent sessions can now share one browser identity, each in its own tabs. Turn it on per identity with "sharing": "tabs" in identity.json (turno identity set browser:<id> --sharing tabs, or the server's --sharing tabs) and serve the identity with exclusive = false in mcp.toml; the default stays one session at a time. Each session gets its own current tab and holds the tabs it works on: another session's call on one of them waits up to 10 seconds and then fails with a message that names the holder. A session lets go of its tabs when it ends (mcpd now tells servers that declare the io.turno/sessions capability), when a tab closes, or after 5 minutes without a call. browser_close closes only the calling session's tabs, tab lists mark the tabs other sessions hold, and the tab governor's cap counts each session's tabs apart. turno identity add browser:<id> --sharing tabs prints the matching mcp.toml block. turno-browser's API version is now 1.4.

  • 3bd7bc2: Follow-ups for browser identities.

    A tool call no longer starts while the tab governor is still closing a popup or a parked tab, so
    the call cannot fail with "Target page, context or browser has been closed". A Chrome that does
    not stop after SIGKILL gets 5 seconds instead of 2 before turno calls it a survivor.

    A server in read mode stops a Lightpanda that a killed server left running on the same cookie jar
    when it starts, and removes its socket folder.

    turno browser doctor warns when an ident...

Read more

turno-browser 0.3.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 00:38
275d91b

What's new in turno 0.3.0: https://turno.wimo.dev/docs/releases/v0-3-0

Minor Changes

  • e806948: browser_batch, useful action errors and the settle setting:

    • New tool browser_batch: runs up to 20 stock browser actions in order in one call, checks
      every action's arguments before running any, stops at the first failure, and returns one line
      per action and one snapshot at the end only when snapshot is true.
    • A browser_click, browser_hover, browser_type, browser_select_option or browser_drag
      that times out because of the element now says which element covers the target (role, name,
      a short selector and its buttons), or that the target is hidden (and by what), disabled,
      read-only or gone, and suggests the next step. Tool names and schemas are unchanged.
    • identity.json settle (like "100ms") sets the wait after each action, Playwright's 500 ms
      by default; --timeout-settle still wins. In a local benchmark of 8 calls it cut the wall
      time of a form fill from about 1.8 s to 0.6 s.
  • cc6b5b2: Browser identity module:

    • identity.json next to each identity's profile keeps its time zone, languages, locale and
      region fixed; Chrome gets them at every start (--accept-lang, --lang, and the time zone
      when it differs from the machine's). turno identity add browser:<id> pins a new identity to
      the current time zone and takes --timezone, --locale, --languages, --region and a
      health check; turno identity show and turno identity set read and change it
      (turno browser show/set <id> too). Without the file nothing changes.
    • A runtime lock ({ nodePid, chromePid, pgid, startedAt }) while an identity's Chrome runs: a
      second session gets a message naming the process and how to stop it instead of "Browser is
      already in use".
    • An optional session health check (a URL and a text or selector) marks a signed-out identity
      NEEDS_AUTH; tool calls then fail with a message that asks for turno browser login <id>.
    • Each captcha, "verify it's you" or block page an identity meets is logged per site (host name
      only); turno browser reputation [<id>] [--json] shows counts and trend.
    • turno browser doctor [--fix] [--no-launch] [--json]: Chrome and its version, a smoke launch,
      the desktop session, and per identity its settings, lock, sign-in and recent challenges, with
      a fix for each problem.
    • mcpd: stop_grace per server in mcp.toml, the wait between closing stdin and SIGTERM;
      5 seconds by default for turno-browser-mcp, the SDK's 2 seconds for every other server.
  • 7779c38: Opt-in resource blocking and resource cache per identity, both off by default:

    • identity.json block: trackers (a built-in list of ad and analytics hosts), types
      (image, media, font) and patterns (host names or URL globs). The page itself is never
      blocked.
    • identity.json cache: keeps images, fonts, stylesheets and scripts on disk for that identity
      only (maxSize, default 100MB, least recently used first), following Cache-Control, never
      storing a response with Set-Cookie or a request with Authorization. Misses still go out
      through Chrome; hits are served from disk.
  • 59309b5: turno browser export <id> --out <file> and turno browser import <file> [--as <id>] move an
    identity's cookies, localStorage and IndexedDB as one file encrypted with a passphrase (scrypt
    and AES-256-GCM), refused after its expiry and never holding vault credentials.
    "keychain": "system" in identity.json makes Chrome encrypt an identity's cookies with the OS
    keychain instead of Playwright's fixed mock key; the default is unchanged.
    turno-browser's API is now 1.2, which this turno requires.

  • 85d9bff: Tab governor:

    • At most 8 pages stay open per session's browser; past that the least recently used one
      closes (never the agent's current tab). Popups that open while no tool call runs, such as a
      pop-under a page opens seconds after a click, are closed; a window the agent's own click opened
      stays.
    • A page unused for 5 minutes is parked on about:blank and stops running; the next call that uses
      it loads its page again. After 15 minutes unused it closes. The next tool result lists what was
      closed or parked, and tab lists mark parked tabs.
    • identity.json (format 2) takes tabs (max, popups, park, close) and
      backgroundThrottling; turno-browser-mcp takes --max-tabs, --popups, --park-after,
      --close-after and --background-throttling, which win over the file.
    • Background tabs keep running at full speed by default, as before: measured, dropping
      Playwright's switches alone has no effect while focus emulation is on, and turning both off
      stalls actions on a tab that is not in front. backgroundThrottling turns both off and brings
      the agent's tab to the front before each call.
  • 50dd77c: Credential vault for browser identities: turno browser vault add|list|remove|submit
    stores a username, a password and an optional TOTP secret per site in the OS secret store, and
    the new browser_login tool fills them into the site's sign-in page without the agent ever
    seeing them. Results and errors are redacted, values are bound to the site's origins, and the
    form is submitted only when the identity opts in. turno-browser's API is now 1.1, which this
    turno requires.

  • fa324c0: Cross-package contracts:

    • turno-browser exports its public API as a typed api object with API_VERSION (1.0).
      turno-cli checks it when it loads the package: a turno-browser that is too old (0.2 and older
      have no API_VERSION) or too new stops turno browser and turno identity browser:<id>
      with one line naming what to update, instead of failing later.
    • mcpd sends every tools/call, from 2025-11-25 sessions and 2026-07-28 requests alike,
      through one call middleware: the profile's tool filter, then the call log, then the session id.
      Refusals and call log records are unchanged.
    • Each relayed tools/call carries _meta["io.turno/session"], an opaque id that is stable for
      one agent session and different for every other. turno-browser-mcp hands it to its own tools
      (session in their context); the Playwright tools are unaffected.
  • 5b46749: Browser lifecycle:

    • turno-browser-mcp passes a generated Playwright MCP --config that closes Chrome after 15
      minutes without a tool call, headed too; the next call opens it again with the same profile.
      TURNO_BROWSER_IDLE changes the limit ("10m", "0" keeps Chrome open); --idle-timeout
      and a --config of your own still win. Flags and tool names are unchanged.
    • On start it closes a Chrome that an earlier, killed run left open on the same profile (only
      a Chrome browser process for exactly that profile whose parent is gone), and on stdin close,
      SIGTERM or SIGHUP it closes Chrome within about 2.5 seconds, forcefully if needed.
    • mcpd stops a quiet session server under critical memory pressure even while its session
      lives; the next call starts it again. turno mcp top counts the process groups a server's
      children lead, so a browser's helpers always count.
    • Docs: one recommendation for browsers, a shared server with exclusive = true per identity
      (the block turno identity add prints), instead of scope = "session".
  • 0537fc1: turno-browser-mcp is now the MCP server host instead of a wrapper that ran the Playwright MCP
    program bundled in patchright-core. It launches Chrome itself through one engine
    module, serves stdio with the MCP SDK, and runs every stock tool through upstream's tool
    backend, so the 25 tool names and input schemas, every flag, TURNO_BROWSER_IDLE, the idle
    close, the orphan sweep and the bounded shutdown work as before. --port keeps upstream's HTTP
    server. initialize now reports turno-browser and its version. A registry for turno's own
    tools is in place (no new tools yet). @modelcontextprotocol/sdk is now a dependency.

Patch Changes

  • 01d17db: The idle limit no longer closes Chrome in the middle of a tool call. It counted from the start of
    the last call, so a call that took longer than TURNO_BROWSER_IDLE (a slow page, a busy machine)
    failed with "Target page, context or browser has been closed". It now stops while a call runs and
    counts from the end of the last one.
  • 2948759: The package homepage is now https://turno.wimo.dev.
  • cf29953: The example time zone in the message for an invalid identity.json and in the help of
    turno identity is now Europe/Madrid.
  • 5566437: Every package has a README that tells the same story as the site. turno-cli's follows the
    order of turno.wimo.dev and lists what the browser gained; turno-browser's is organized around
    what the package does (identities, the credential vault, session export and import, tab limits,
    browser_batch, blocking and cache, health and doctor); turno-core's says what the shared
    package is for; turno-fonts' shows the status line and how turno ui install uses the font.
    Each links to its page on turno.wimo.dev and to the releases.
  • a0bfce8: New package turno-core with what turno-cli and turno-browser share: turno's paths, the secret
    store (macOS Keychain, Linux Secret Service) and the process helpers. Both packages
    now depend on it instead of keeping their own copies; behavior is unchanged.
  • Updated dependencies [2948759]
  • Updated dependencies [5566437]
  • Updated dependencies [a0bfce8]
    • turno-core@0.1.0

A CycloneDX SBOM is attached.

turno-cli 0.2.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 00:47
fc5e764

See CHANGELOG.md of turno-cli. SBOM attached.

turno-browser 0.2.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 00:46
fc5e764

See CHANGELOG.md of turno-browser. SBOM attached.

turno-fonts 0.1.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:09
c26efcd

See CHANGELOG.md of turno-fonts. SBOM attached.

turno-cli 0.1.1

Choose a tag to compare

@github-actions github-actions released this 16 Nov 19:09
c26efcd

See CHANGELOG.md of turno-cli. SBOM attached.