Check CLI Status
Inspect the active CLI profile, token source, and workspace defaults before you run commands.
Inspect the active CLI profile, token source, and stored workspace defaults before you continue.
- See the active profile clearly.
- Know which token is in use.
- Catch a wrong workspace before acting.
Where this happens
Do the work
- 1. Run `./backlog.sh status`.
- 2. Read the active profile, base URL, auth mode, and stored workspace id.
- 3. Check the token source so you know whether the CLI is using flags, environment, or stored secrets.
- 4. Only continue once the displayed state matches the workflow you intend to run.
Keep Going in CLI Setup
Stay in the same interface and move to the next closest task in this topic when needed.
Download the CLI
Download the standalone Backlog CLI script from `https://backlog.to/backlog.sh` and make it executable locally.
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.
Configure a CLI Profile
Persist the base URL or workspace id for a CLI profile so repetitive commands stop depending on long flag strings.
Inspect the Current Workspace Context
Check who the current principal is, which workspace is active, and which installation context is in effect before you run sensitive automation or admin work.