Download the CLI
Download the standalone Backlog CLI script from `https://backlog.to/backlog.sh` and make it executable locally.
The Backlog CLI is distributed as a single shell script rather than a package manager install.
That means the fastest path is to open `https://backlog.to/backlog.sh` or download it with `curl`, mark it executable, and run it from wherever you keep local tools.
The CLI is shipped as one downloadable shell script, so setup starts with saving `backlog.sh` locally and marking it executable.
- Download the script directly.
- Make the file executable.
- Run the CLI locally before deeper setup.
Where this happens
Do the work
- 1. Open `https://backlog.to/backlog.sh` in a browser and save the file, or run `curl -fsSL https://backlog.to/backlog.sh -o backlog.sh` in the terminal.
- 2. Run `chmod +x backlog.sh` so the file can execute locally.
- 3. Run `./backlog.sh --help` to confirm the script starts correctly.
- 4. Keep using `./backlog.sh` directly, or move it into a directory already on your shell `PATH` if you want a shorter command later.
Keep this clear
- The public asset at `https://backlog.to/backlog.sh` always serves the current CLI script from the Backlog site.
- The docs use `./backlog.sh` in examples, but the filename or final install location is up to you.
Shell example
curl -fsSL https://backlog.to/backlog.sh -o backlog.sh
chmod +x backlog.sh
./backlog.sh --helpKeep Going in CLI Setup
Stay in the same interface and move to the next closest task in this topic when needed.
Check CLI Status
Inspect the active CLI profile, token source, and workspace defaults before you run commands.
Configure a CLI Profile
Persist the base URL or workspace id for a CLI profile so repetitive commands stop depending on long flag strings.
Set the Active CLI Token
Switch the CLI into the right token mode before you run resource or admin commands.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.