Skip to content

Install

Condr ships in two deployment forms:

Form Best for Components
Desktop app (recommended) Everyday local development and interaction GUI + bundled Server
Headless Server Remote servers, cloud hosts, GUI-less containers and dev machines condr CLI and Server only

The desktop app bundles the Server and starts it automatically when the app opens, so there is no background service to configure separately. To connect to this device remotely, see Remote connections.

Get the package for your platform from the download center:

Platform Architecture Package
macOS Apple Silicon .dmg
Windows x86_64 .exe
Linux x86_64 / arm64 .AppImage

Windows The installer is not code-signed yet. If SmartScreen blocks it, click More info → Run anyway.

Linux After downloading, make the AppImage executable and launch it:

Terminal window
chmod +x condr-*-linux-*.AppImage
./condr-*-linux-*.AppImage

Tip: if your environment lacks FUSE support, add this flag to extract and run it directly:

Terminal window
./condr-*-linux-*.AppImage --appimage-extract-and-run

In environments without a graphical interface, only the condr CLI needs to be installed.

Linux / macOS:

Terminal window
curl -fsSL https://condr.dev/install.sh | sh

Windows (PowerShell):

Terminal window
irm https://condr.dev/install.ps1 | iex

The install script places the binary in the directory below and adds it to your PATH automatically:

  • Linux / macOS: ~/.local/opt/condr
  • Windows: %LOCALAPPDATA%\Programs\Condr

Reopen your terminal and verify the installation:

Terminal window
condr --version
Terminal window
condr server start

The Server runs as a daemon; closing the current terminal does not affect it.

Note: no system startup service is registered yet, so after a host reboot you need to run this command again by hand.

3. Advanced install and environment options

Section titled “3. Advanced install and environment options”

Environment variables let you switch release channels, pin a version or force a reinstall:

Linux / macOS:

Terminal window
# Switch to the daily Nightly build
curl -fsSL https://condr.dev/install.sh | CONDR_VERSION=nightly sh
# Install a specific version
curl -fsSL https://condr.dev/install.sh | CONDR_VERSION=v0.1.0 sh
# Force-reinstall the current version
curl -fsSL https://condr.dev/install.sh | sh -s -- --force

Windows (PowerShell):

Terminal window
# Switch to the daily Nightly build
$env:CONDR_VERSION = 'nightly'; irm https://condr.dev/install.ps1 | iex
# Install a specific version
$env:CONDR_VERSION = 'v0.1.0'; irm https://condr.dev/install.ps1 | iex
# Force-reinstall the current version
$env:CONDR_INSTALL_ARGS = '--force'; irm https://condr.dev/install.ps1 | iex

By default, Condr checks its channel for updates in the background every 5 hours. You can see the version status in the client under Settings › About › Updates.

Channel What it is Who it is for
Stable Tested, standard stable releases (default) Most production and everyday use
Nightly Built automatically from the main branch every day, with the latest features Early adopters, feature testing and bug verification

Compatibility note: the client and Server versions need to match. If the two sides differ in version but the protocol is compatible, the sidebar shows a yellow warning icon; if the protocol is incompatible, the connection is refused.

Download the new version and install it over the old one. The old Server is handled as follows:

  • Windows: the installer stops the old Server automatically, and the new Server is started when you launch the new client.
  • macOS / Linux: the old Server keeps running after installation. The new client prompts you to restart the service when it launches; you can also do it later by clicking Restart Condr under Settings › General.

Run the matching install script again; it detects the current install and updates it in place.

If it finds a Server running, the script asks whether to restart it now:

  • Restart now: the new version takes effect immediately.
  • Restart later: the current process keeps running, and the switch completes once you restart it by hand.

About the impact of a restart: restarting the Server interrupts every running Pane process. Afterwards, Condr restores the Workspaces, Tabs and Pane layout from the snapshot. Agents with Hooks configured resume their sessions automatically; see Workspaces, Tabs and Panes.


Uninstalling removes only the application itself and its executables. It does not delete your configuration, runtime state or local logs. To remove the remaining data completely, see Configuration and settings and clean up the directories by hand.

Install type How to uninstall
Windows desktop app Uninstall it under Settings › Apps › Installed apps. The installer stops the background service and cleans up the environment variables automatically.
macOS desktop app Move Condr.app to the Trash, then run the cleanup command below.
Linux desktop app Delete the .AppImage file, then run the cleanup command below.
Headless Server Run the cleanup command directly.

Step 2: remove the CLI and background service

Section titled “Step 2: remove the CLI and background service”

In a regular system terminal, not a terminal inside Condr, run:

Terminal window
condr server uninstall

After confirmation, this command stops the running Server process and deletes the condr binary together with its PATH entry. In scripted environments, add --yes to skip the interactive confirmation: condr server uninstall --yes