scoop install sdods gave me the app, not the sdods command — where is the CLI on Windows?

Asked 28 May 20262,210 views3 answers

14votes

Added the bucket and installed:

powershell

scoop bucket add sdods https://github.com/YarlisAISolutions/scoop-sdods
scoop install sdods

I now have a desktop application. What I wanted was sdods run in a terminal. Did I pick the wrong package name?

asked by Fiona McAllister159 · 28 May 2026

3 answers

18votes✓
Accepted answer
Right name, wrong channel for what you want. Scoop and winget both install the desktop app — they are the managers Windows users already have, and a GUI installer is what they are built to place.
The CLI on Windows comes from the PowerShell script or from npm:
powershell
```
irm https://sdods.com/install.ps1 | iex
```
powershell
```
npm install -g @sdods/cli
```
Both give you sdods on PATH. Having the app as well is fine — they are separate things and do not conflict.
answered by Sam Orbison9,420 · 28 May 2026
8votes
Worth reading the channel table with that split in mind: it lists three different products. The scripts, npm and Homebrew install the CLI; Docker installs the server and web UI; Scoop, winget and the Debian packages install the desktop app.
The whole table is in Getting started → Installation, with what each one needs.
answered by Daniel Oyelaranmaintainer24,177 · 29 May 2026
4votes
If you install both, keep in mind that upgrading one does not upgrade the other. scoop update sdods moves the app; the CLI moves when you re-run the script or update the npm package. Ours drifted apart for a month before anyone noticed.
answered by Hsu Wei-lin15,230 · 2 Jun 2026

Have a different question? Ask it.