# Releases (/docs/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.

<ReleaseLine>
<Release latest version="0.4.0" date="2026-11-19" href="/docs/releases/v0-4-0" packages={["turno-cli@0.4.0","turno-browser@0.4.0"]}>
One browser for several agents. A browser identity can **[serve several agent sessions at once](/docs/browser/sharing)**, each in its own tabs, **[record a flow and replay it](/docs/browser/flows#flows-record-and-replay)**, be **[driven from the shell](/docs/browser/actions#from-the-shell)** and **[show you the agent's tab so you can take over](/docs/browser/live-view)**. Lightpanda and your own Chrome join as **[engines](/docs/browser/engines)**. Every new setting is off until you turn it on.
</Release>

<Release version="0.3.0" date="2026-11-18" href="/docs/releases/v0-3-0" packages={["turno-cli@0.3.0","turno-browser@0.3.0","turno-core@0.1.0","turno-fonts@0.1.2"]}>
A browser your agents can sign in with and carry between machines. `turno-browser` **[signs in to a site without showing the password to the model](/docs/browser/vault)**, **[moves a signed-in session to another machine](/docs/browser/moving-a-session)** and **[keeps tabs under control](/docs/browser/tabs#tabs)**. The CLI gets **[a stable output contract for scripts](/docs/reference/json-output)**, diagnostics you can paste into an issue, and a safe mode. After upgrading, run `turno mcp sync` once.
</Release>

<Release version="0.2.0" date="2026-11-17" href="/docs/releases/v0-2-0" packages={["turno-cli@0.2.0","turno-browser@0.2.0"]}>
A new look for the CLI and a gateway that does more with less. **[`turno init`](/docs/get-started/first-five-minutes)** sets everything up in one step, **[server sets](/docs/concepts/folder-rules#server-sets-which-mcp-servers-a-folder-sees)** let each folder see only its MCP servers, the gateway signs in to **[remote servers with OAuth](/docs/concepts/gateway#remote-servers)** once per account, and **[`turno mcp top` and `turno mcp log`](/docs/concepts/gateway#watching-it)** show what it does. After upgrading, run `turno mcp sync` once.
</Release>

<Release version="0.1" date="2026-11-16" href="/docs/releases/v0-1-0">
The first public release: one MCP gateway for every agent session, profiles for four coding agents and the Claude Code status line.
</Release>
</ReleaseLine>

## Upgrade [#upgrade]

<Upgrade />

To see the version you have, run `turno version`; `turno upgrade --check` only asks the registry whether there is a newer one.

## Versions [#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.