> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loongclaw.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install Loong from release artifacts or source.

# Installation

Loong prefers a release-first install path.

## Choose An Install Path

| If you want to...                                      | Use this path                        |
| ------------------------------------------------------ | ------------------------------------ |
| follow the intended end-user path                      | the release-first installer          |
| work from an active checkout or validate local changes | source install                       |
| land in onboarding immediately after install           | either install path with `--onboard` |

## Recommended Install

```bash theme={null}
curl -fsSL https://raw.githubusercontent.com/eastreams/loong/dev/scripts/install.sh | bash -s -- --onboard
```

Windows PowerShell:

```powershell theme={null}
$script = Join-Path $env:TEMP "loong-install.ps1"
Invoke-WebRequest https://raw.githubusercontent.com/eastreams/loong/dev/scripts/install.ps1 -OutFile $script
pwsh $script -Onboard
```

## What This Does

* The installer prefers checksum-verified GitHub Release binaries.
* On Linux x86\_64, GNU and musl artifacts are treated separately.
* `loong` is the supported command-line entrypoint.
* The install path is meant to hand you directly into first run rather than stop at a raw binary drop.

## Source Install

```bash theme={null}
bash scripts/install.sh --source --onboard
```

```bash theme={null}
cargo install --path crates/daemon
```

## After Install

Run the supported first-run path next:

```bash theme={null}
loong
```

If you want the shortest full path, continue directly to:

```bash theme={null}
loong ask --message "Summarize this repository and suggest the best next step."
```

Reopen the deeper guided setup flow later with:

```bash theme={null}
loong onboard
```

## Which Path To Choose

* Use the release-first installer when you want the intended end-user path.
* Use source install when you are developing locally, validating changes, or working from an active checkout.
* Prefer `--onboard` unless you have a specific reason to stop before first run.

## What Comes Next

* Continue to [First Run](/get-started/first-run) for onboarding and your first useful answer.
* Go to [Doctor And Health](/get-started/doctor-and-health) if you need the repair path before the first run completes cleanly.