Releases
What is new in each version of turno.
One page per version: what changed, how to use it and what to run when you upgrade. Each package's full changelog is on GitHub, and each GitHub release links back here.
turno 0.4.0
- turno-cli0.4.0
- turno-browser0.4.0
Read the release notes for turno 0.4.0One browser for several agents. A browser identity can serve several agent sessions at once, each in its own tabs, record a flow and replay it, be driven from the shell and show you the agent's tab so you can take over. Lightpanda and your own Chrome join as engines. Every new setting is off until you turn it on.
turno 0.3.0
- turno-cli0.3.0
- turno-browser0.3.0
- turno-core0.1.0
- turno-fonts0.1.2
Read the release notes for turno 0.3.0A browser your agents can sign in with and carry between machines.
turno-browsersigns in to a site without showing the password to the model, moves a signed-in session to another machine and keeps tabs under control. The CLI gets a stable output contract for scripts, diagnostics you can paste into an issue, and a safe mode. After upgrading, runturno mcp synconce.turno 0.2.0
- turno-cli0.2.0
- turno-browser0.2.0
Read the release notes for turno 0.2.0A new look for the CLI and a gateway that does more with less.
turno initsets everything up in one step, server sets let each folder see only its MCP servers, the gateway signs in to remote servers with OAuth once per account, andturno mcp topandturno mcp logshow what it does. After upgrading, runturno mcp synconce.turno 0.1
Read the release notes for turno 0.1The first public release: one MCP gateway for every agent session, profiles for four coding agents and the Claude Code status line.
Upgrade
One command
turno upgradeUpdates 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@latestThen run turno upgrade --finish: it rewrites the launchers, checks the config and shows what changed.
To see the version you have, run turno version; turno upgrade --check only asks the registry whether there is a newer one.
Versions
turno follows semantic versioning. While it is below 1.0, a minor version (0.3, 0.4) can change behavior, and its page says what changed under "Changed behavior". A patch release has no page of its own: its fixes are in the changelogs. turno-cli and turno-browser move together; turno-core and turno-fonts follow their own numbers.