Install the CLI
Install the public executable, separately from the access-controlled Framework, and check its version.
Before you install
The public installer downloads one platform executable, checks its archive checksum, and confirms that the executable reports the requested version. It installs only the CLI: the Framework, application dependencies, model weights, and credentials come later. You can install the CLI and use its local context and MCP features without Framework access.
The examples pin CLI 0.0.17. Read the downloaded script before running it, and run it as your normal user. To update the CLI later, rerun the installer with the published version you want; this does not change any application's Framework packages.
macOS and Linux
curl --fail --silent --show-error https://get.smoothie.dev/install.sh -o smoothie-install.sh
# Review smoothie-install.sh before running it.
bash smoothie-install.sh --version 0.0.17
export PATH="$HOME/.smoothie/bin:$PATH"
smoothie --versionThe last command should print Smoothie CLI 0.0.17. The executable is installed in ~/.smoothie/bin. The installer configures future Bash, Zsh and Fish shells; the export above makes it available in the current terminal. Existing user-owned, writable symlinked profiles are updated without replacing their links. Use --no-modify-path to leave profiles untouched. Unsupported shells or unusable profiles receive manual PATH instructions. If the installer stops, read its message: it keeps any previous installation and never needs root or a bypassed checksum.
Windows PowerShell
Invoke-WebRequest https://get.smoothie.dev/install.ps1 -OutFile smoothie-install.ps1
# Review smoothie-install.ps1 before running it.
& .\smoothie-install.ps1 -Version 0.0.17
$env:Path = "$env:USERPROFILE\.smoothie\bin;$env:Path"
smoothie --versionThe installer updates User PATH and its current PowerShell session. A separate -File process requires a new terminal. Use -NoModifyPath to opt out. If PowerShell refuses to run the script, ask your administrator which execution policy applies; do not weaken it just to follow this guide.
CLI 0.0.17 passed native Windows executable and installer qualification. Private upstream writes and native project checks remain unavailable on Windows, and a separate post-publication Windows install was not rerun. Use macOS ARM64 or Linux x64 to follow the complete first-application tutorial.
Check the executable
smoothie help framework acquire
smoothie licensesHelp shows the acquisition command you will use next, and licenses prints the bundled CLI license and notices. Neither command contacts GitHub or reads a project. If smoothie is not found or reports another version, run command -v smoothie (Get-Command smoothie in PowerShell) to see which executable your shell resolves.
CLI 0.0.17 and Framework 0.1.0 are separate releases with separate versions. A published CLI does not approve every Framework package, host, or deployment workflow. See Compatibility for what this path covers.
Next step
Continue with Obtain a Framework release. You need a GitHub account with Framework access and the GitHub CLI installed. Bun and Node are needed later to run the application.