---
name: encore-install
description: Install the Encore CLI, check whether it's installed, put it on the PATH, update it, and check what local development needs (Docker, plus Node.js for Encore.ts). The same steps work for Encore.ts and Encore.go.
when_to_use: >-
  The `encore` command isn't installed or isn't found, the user wants to install, set up, update, or upgrade the Encore CLI, or a task needs the CLI before any other Encore step (creating, running, testing, or deploying an app). Also use when `encore run` or `encore test` fails because Docker isn't installed or isn't running. Trigger phrases: "install Encore", "set up Encore", "encore: command not found", "brew install encoredev/tap/encore", "install.sh", "update Encore", "upgrade the Encore CLI", "encore version update", "docker daemon is not running".
title: encore-install
canonical_url: https://skilld.dev/gh/encoredev/skills/install
last_updated: 2026-10-27T15:20:19.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install encoredev/skills/install`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/install`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/encoredev/skills/install) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/install`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/install --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/install --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Installing the Encore CLI

## Instructions

Do the steps in order.

### 1. Check whether it's installed

```bash
encore version
```

- **Prints `encore version v...`:** installed. Go to step 4.
- **Command not found:** run `~/.encore/bin/encore version`. If that prints a version, Encore is installed but not on the PATH: go to step 3. Otherwise go to step 2.

### 2. Install

Ask the user first, unless they asked you to install Encore. Run the command for the OS. None of them prompt for input.

```bash
# macOS
brew install encoredev/tap/encore

# Linux, WSL, or macOS without Homebrew
curl -L https://encore.dev/install.sh | bash

# Windows (PowerShell)
iwr https://encore.dev/install.ps1 | iex
```

Run `encore version` again. If it's still not found, go to step 3. On Windows, open a new shell instead: the installer adds `%USERPROFILE%\.encore\bin` to the PATH, but shells that were already open don't see it.

### 3. Put it on the PATH

`install.sh` installs to `~/.encore/bin` and doesn't edit shell profiles. Add it to the PATH:

```bash
export ENCORE_INSTALL="$HOME/.encore"
export PATH="$ENCORE_INSTALL/bin:$PATH"
```

Agent shells often drop environment variables between commands. Prefix each `encore` command with these exports, or call `~/.encore/bin/encore` by its full path. To make it permanent, ask the user, then add the two lines to their shell profile (`~/.zshrc` for zsh, `~/.bashrc` for bash).

### 4. Check what the app needs

| Tool | Needed for | Check | If it fails |
|------|------------|-------|-------------|
| Docker | Apps with SQL databases (`encore run`, `encore test`) | `docker info` | Not installed: ask the user to install Docker. Not running: start it (macOS: `open -a Docker`) and wait until `docker info` succeeds |
| Node.js and npm | Encore.ts apps | `node --version` | Ask the user to install Node.js |
| git | Creating apps and deploying | `git --version` | Ask the user to install git |

Encore.go needs no separate Go install: the CLI includes the Go toolchain it builds with. Other local infrastructure (Pub/Sub, caches, buckets, cron) runs without Docker.

## Updating

```bash
encore version update
```

This uses Homebrew if Encore was installed with it, and the install script otherwise. Then update the app's `encore.dev` package to match: `npm install encore.dev@latest` (Encore.ts) or `go get encore.dev@latest` (Encore.go).

## Guidelines

- When `encore` isn't found right after installing, fix the PATH (step 3). Don't install again.
- Ask before installing software or editing shell profiles, unless the user asked you to.
- Next: log in (`encore-login`), create an app (`encore-create-app`), and run it (`encore-run`).
- Docs: https://encore.dev/docs/quick-start
