# Install (/docs/get-started/install)

Install turno with npm, pnpm, bun, yarn or Homebrew, on macOS or Linux.

This page installs the `turno` command and shows how to update and remove it.

## Requirements [#requirements]

- macOS or Linux. Windows is not supported.
- Node 22.11 or newer.
- At least one of the agents turno works with: Claude Code, Codex CLI, GitHub Copilot CLI or Cursor CLI.

## Install the CLI [#install-the-cli]

The npm package is `turno-cli`; the command it installs is `turno`.

<Install pkg="turno-cli" />

Check it:

```sh
turno version
```

`turno upgrade` later updates turno with the same tool that installed it. CI installs the packed release with each of these on macOS and Linux and runs it.

- The package runs no install scripts, so pnpm and bun, which block dependencies' scripts by default, need no approval.
- npm and Homebrew install exactly the dependency versions that were tested, from the package's `npm-shrinkwrap.json`. pnpm, bun and yarn do not read that file: they install the same direct dependencies (pinned to exact versions) and resolve the dependencies of those themselves.
- pnpm 11 and later wait a day before they install a new release (`minimumReleaseAge`), so a release reaches pnpm a day after npm.
- yarn means yarn 1 (classic). yarn 2 and later have no global installs: use npm, pnpm or bun there.

## Run it once without installing [#run-it-once-without-installing]

```sh
npx turno-cli demo
pnpm dlx turno-cli demo
bunx turno-cli demo
```

`turno demo` works from there, in a throwaway HOME. Commands that write launchers or the status line refuse to run from a one-off copy, because the runner may delete its cache at any time: install turno first.

## Linux [#linux]

Linux works too: MCP secrets go to the Secret Service (`secret-tool`, from libsecret), the gateway runs as a `systemd --user` unit, and links open with `xdg-open`.

## The browser package (optional) [#the-browser-package-optional]

`turno-browser` is a separate package, not installed with turno; turno works without it. Install it only if you want an agent to drive your signed-in Chrome ([guide](/docs/guides/signed-in-browser)).

<Install pkg="turno-browser" />

## Shell completion (optional) [#shell-completion-optional]

```sh
echo 'source <(turno completion zsh)' >> ~/.zshrc
echo 'source <(turno completion bash)' >> ~/.bashrc
turno completion fish > ~/.config/fish/completions/turno.fish
```

It completes commands, profiles, identities and config keys.

## Update [#update]

```sh
turno upgrade --check   # is there a newer release?
turno upgrade           # update turno the way it was installed
```

Interactive commands ask the npm registry for a newer version at most once a day, sending only the package name. Turn that off with `update_check = false` in config.toml or `TURNO_NO_UPDATE_CHECK=1` ([more ways](/docs/security#when-turno-goes-online)).

## Uninstall [#uninstall]

```sh
turno uninstall --dry-run   # lists what turno set up: service, launchers, MCP entries, status line, config
turno uninstall             # removes it
npm uninstall --global turno-cli   # or: pnpm remove --global, bun remove --global, yarn global remove, brew uninstall turno
```

Profile folders, which hold your logins, stay until you delete them. `turno uninstall --purge` also removes turno's state and caches (backups, logs, usage, installed MCP servers), after which `turno undo` has nothing to restore.

## Next [#next]

[First five minutes](/docs/get-started/first-five-minutes): set turno up with `turno init`.