Install Concierto

Three ways to get Concierto running. The Mac app, the CLI + daemon, or a self-hosted backend. Pick the one that matches how your team works.

There are three ways to run Concierto. They are not mutually exclusive. Most people start with the Mac app, and reach for the CLI when they want to script the platform or run agents in CI.

No. 01

Mac app

Native multi-tab window with the CLI built in. It starts the daemon for you on launch, nothing to run by hand. Best for daily use.

Recommended

No. 02

CLI + daemon

The concierto binary and the daemon that drives your local AI coding tools. The layer the apps wrap; ideal for scripting and headless agents.

Power users · CI

No. 03

Self-host

Run the whole backend on your own infrastructure. Database, server, and storage all stay on your machines.

Docker · Helm

Where do agents run? Concierto's server stores your work and coordinates it, but agent tasks execute on a runtime, today that means a daemon on your own machine driving a local AI coding tool. Read How Concierto works for the 30-second model before you install.

Option 1, The Mac app

The fastest path. The Mac app bundles the concierto CLI and launches its own daemon profile on startup, so once you sign in your agents are ready to work, zero commands.

concierto.nstack.ai/download

Screenshot · capture pendingDownload · concierto.nstack.ai/download

The download page auto-detects your platform and starts the Apple-Silicon .dmg. Other builds (Intel, Windows, Linux) are one click below.

Download the installer

Open the Concierto downloads page. The Apple-Silicon .dmg starts automatically; pick another build under Other platforms if you need Intel, Windows, or Linux.

Move it to Applications

Open the .dmg and drag NSTACK Concierto into your Applications folder.

First launch

Concierto isn't notarized yet, so the first open needs one extra click: right-click the app → Open → Open anyway. Prefer the terminal? Clear the quarantine flag instead:

xattr -d com.apple.quarantine "/Applications/NSTACK Concierto.app"
open "/Applications/NSTACK Concierto.app"

Installing the Mac appVideo coming soon · ≈ 90 sec

Walkthrough: download → drag to Applications → first-launch approval → sign in → first agent online.

See Desktop app for tab groups, auto-updates, and pointing Desktop at a self-hosted backend.

Option 2, The CLI + daemon

The concierto CLI mirrors almost everything the web app can do, and the daemon is what actually runs agents on your machine.

Prerequisite: at least one AI coding tool installed locally. Claude Code, Codex, Cursor, Copilot, Gemini, and others. The daemon auto-detects them on startup and refuses to start if none are present.

Install the binary

macOS / Linux (Homebrew, recommended)

brew install nstack-enterprises/tap/concierto

macOS / Linux (no Homebrew)

curl -fsSL https://raw.githubusercontent.com/nstack-enterprises/concierto-agent-platform/main/scripts/install.sh | bash

Windows (PowerShell)

irm https://raw.githubusercontent.com/nstack-enterprises/concierto-agent-platform/main/scripts/install.ps1 | iex

Verify it's on your PATH:

concierto version

Log in and start the daemon

A single command logs you in and brings the daemon online:

concierto setup

This configures the CLI for Concierto Cloud, opens your browser to authenticate, stores a personal access token in ~/.concierto/config.json, and starts the daemon, which begins polling for tasks every 3 seconds and sending heartbeats every 15 seconds.

Confirm the daemon is online

concierto daemon status

online means it has registered with the server. See the full CLI command reference and Authentication and tokens for headless/CI login.

Option 3, Self-host the backend

Run the server, database, and object storage on your own infrastructure with Docker Compose or Helm. Your daemon and agents still run wherever you choose; only the control plane moves.

Quickest path: Docker Compose

git clone https://github.com/nstack-enterprises/concierto-agent-platform.git
cd concierto-agent-platform
cp .env.example .env   # set your secrets and FRONTEND_ORIGIN
docker compose up -d

Self-host has its own setup surface. Read the Self-host quickstart for the full walkthrough and the Environment variables reference (especially FRONTEND_ORIGIN, which gates invite links and WebSocket origin checks).

Verify your runtime is online

However you installed, confirm a runtime is registered before assigning work. In the app, open Settings → Runtimes, your daemon appears as one or more active runtimes (one per AI coding tool it detected).

Concierto · Settings → Runtimes

Screenshot · capture pendingSettings · Runtimes

A healthy runtime shows online with its provider and concurrency. If it's offline, see Troubleshooting → Daemon can't reach the server.

Next steps

Ship something in five minutes

The Quickstart takes you from a one-line idea to a shipped Track, the zero-shot flow.

Understand the runtime model

How Concierto works. Where the server, daemon, and AI tool each fit.

Connect to Cloud or self-host

Cloud quickstart or Self-host quickstart, depending on where your backend lives.