What your computer needs #

View this page as Markdown

On this page

To connect to Turn Zero Cloud, you need a supported AI client and a browser for the first sign-in. Your AI tool can check and install the software needed to build and deploy from your computer. You may need to approve changes or complete a step the tool cannot run.

Chat clients can deploy small applications through deploy_files without installing the local build tools below.

Before you start, read the application and storage limits. An account can hold 10 applications. You can read the current limits without signing in.

The list #

  • A supported AI client. Connect your AI assistant covers Claude Code, Codex, the Claude apps, and ChatGPT.
  • Node.js 24 or later, for local builds and deploys. The platform runs Node.js 24. The turnzero command also requires Node.js 24 or later.
  • npm, for local builds and deploys. It ships with Node.js and installs the application's dependencies.
  • The turnzero command, for local deploys. Your AI tool first runs it through npx, without a global installation. Install the turnzero command explains the optional global install.

A local deploy needs a credential supplied to the command or stored on this computer. Your AI tool follows Authorize this computer for deploys. To authorize this computer yourself, run turnzero login in your own terminal, or turnzero login --device and approve its link on any device.

Cloud itself requires no SDK, compiler, signing certificate, or separate console. Deploying requires neither Git nor a Git repository.

For the AI tool: The rest of this page addresses you directly. Check what is already installed before making changes. If a step needs the person, tell them what to do and wait for their response.

Do not assume Git is installed. Before using a Git command such as git diff, check that git is available. The turnzero command can read a repository's commit without running Git; see What it reads.

Before giving the person a command #

If the person will run the commands, give them this checklist before their first command:

  • Check node --version: it must show 24 or later. If Node.js is missing or older, follow Check your Node.js version, including its Windows installer or archive route.
  • On Windows, use npx.cmd and npm.cmd with the same arguments. PowerShell's default execution policy blocks the script forms; do not change that policy.
  • If computer authorization needs browser sign-in, explain the prompt first. The person signs in and approves access in their browser.

Check your Node.js version #

The commands below use bash or zsh on macOS and Linux. On Windows, read Windows PowerShell first.

Check the Node.js and npm versions.

node --version
npm --version

The Node.js version must be v24 or later. If Node.js or npm is missing, or Node.js is too old, install Node.js 24 or later and run both checks again.

Use the existing installation method to update Node.js. For Homebrew, run brew install node@24 and follow its instructions to put that version first on PATH. For nvm or fnm, install version 24 through that manager. Do not run npm install -g node; it can conflict with the existing installation (npm install -g node ends with EEXIST).

For a new installation, use the installer from nodejs.org or a Node.js version manager. If the machine cannot run an installer, use the Node.js 24 archive from nodejs.org: .tar.gz for macOS or Linux, or .zip for Windows. Check its SHA-256 against the accompanying SHASUMS256.txt, using shasum -a 256 <file> on macOS, sha256sum <file> on Linux, or Get-FileHash <file> on Windows.

Unpack the archive into the person's home folder. It creates a versioned folder, such as node-v24.11.0-darwin-arm64. Add its bin folder to PATH; on Windows, add the unpacked folder itself. Make the change persistent in the shell profile on macOS or Linux, or in the user's environment variables on Windows. Start a new shell session and run both checks again.

Once node --version shows 24 or later in the same shell, run the returned npx line unchanged. Do not wrap it in another npx command to select Node.js (npm EUSAGE).

Install the turnzero command #

Your AI tool first uses the returned command_npx, or command_npx_windows on Windows. This needs Node.js and npm, but no global turnzero installation.

If npx can't run here, use the installed command when turnzero --version responds. Otherwise, for a deploy use deploy_files within its limits, then the upload route past them. Install the command only if the person wants to keep it.

To install globally, run npm install -g turnzero. If that command can't run here, try another available deployment route before asking the person for a step. The installed version stays fixed until another install.

On macOS and Linux, a global install can fail with EACCES if npm's global folder belongs to the system. Do not use sudo. Configure a global folder under the person's home directory:

  1. Run npm config set prefix ~/.npm-global.
  2. Add ~/.npm-global/bin to PATH in the person's shell profile.
  3. Start a new shell session and run the install again.

A Node.js version manager also avoids this permissions problem by using a folder owned by the user.

To write a command without a global installation, use npx --no-update-notifier -y turnzero@latest in place of turnzero, or npx.cmd on Windows. AI tools use the returned npx form first. Ways to deploy to Turn Zero Cloud explains what to do if it cannot run. npm may print nothing for several seconds while it downloads the package. The command's first output line names its version.

Windows PowerShell #

On Windows, prefer PowerShell 7 for its HTTP and UTF-8 support. Execution policy and the tools you invoke still matter: use the returned Windows command and the documented ZIP procedure. Install PowerShell 7 with winget, included in current Windows 10 and Windows 11.

winget install --id Microsoft.PowerShell --source winget

Run subsequent commands in PowerShell 7 (pwsh) instead of Windows PowerShell.

If using Windows PowerShell 5.1, apply these five adjustments to the commands on these pages:

  • npm and the turnzero command. In Windows PowerShell, the default execution policy, a machine setting, blocks scripts. In it, npm and the installed turnzero are scripts. Run npm.cmd with the same arguments, and turnzero.cmd in place of turnzero. Returned commands have Windows forms using turnzero.cmd or npx.cmd. For a command that no tool call returns, such as turnzero hash or an unattended turnzero deploy, write turnzero.cmd in place of turnzero. For npx, write npx.cmd in place of npx.
  • A script you write. The same policy blocks a .ps1 file you write. This is the computer's policy; the platform ships no PowerShell script. Run it for one process with powershell -NoProfile -ExecutionPolicy Bypass -File <script>, which leaves the machine's policy as it is. Or run the script's commands inline in the session instead. An inline node -e script loses its double quotes on the way to node, as an inline JSON body does. Write single quotes inside it, or pipe the script to node -.
  • A request that must see an error status. In Windows PowerShell 5.1, Invoke-WebRequest fails on a 4xx or 5xx response, and it lacks the -SkipHttpErrorCheck switch that PowerShell 7 added to return that response. Run curl.exe instead. Type it with its .exe, because curl alone is another name for Invoke-WebRequest in Windows PowerShell 5.1. curl.exe -i shows the response's status.
  • The artifact zip. The turnzero command builds the application's zip. If you build the zip yourself, use tar.exe, as Build and upload the artifact shows. Don't use Compress-Archive: it writes \ in the names of the files inside the zip, and the deploy refuses a zip with those names.
  • A JSON request body. In Windows PowerShell 5.1, -Encoding utf8 on Set-Content and Out-File writes a byte-order mark, which a JSON parser rejects. Windows PowerShell 5.1 has no -Encoding utf8NoBOM, which PowerShell 7 added. Write the body with [System.IO.File]::WriteAllText("$env:TEMP\body.json", $json), which writes none, and send it with curl.exe --data-binary "@$env:TEMP\body.json". The file is outside the application's folder, so the next deploy does not ship it. A file also keeps the body's double quotes, which an inline body such as --data '{"title":"first"}' loses on its way to curl.exe.

In either PowerShell, save a downloaded file before you check its bytes. Invoke-WebRequest -OutFile or curl.exe -o saves the bytes as they arrived, and Get-FileHash gives each saved file's hash to compare. Don't check a response's .Content instead. .Content can hold the body decoded as text, which changes its bytes.