aclilisted

# Atlassian CLI (acli) Interact with Atlassian Cloud — Jira work items, projects, sprints, boards, filters, and Confluence content — using the `acli` CLI. ## Prerequisites - `acli` must be installed (`acli --version` to check) and authenticated - OAuth (Jira + Confluence together): `acli auth login` - Product-scoped OAuth: `acli jira auth login --web` / `acli confluence auth login` - API token: `acli jira auth login --site <site>.atlassian.net --email <you>@... --token` - Verify with `acli auth status` (global) or `acli jira auth status` / `acli confluence auth status` - For multi-account setups, switch the active account with `acli jira auth switch` / `acli confluence auth switch` - **Headless environments (containers, CI, remote shells):** `--web` OAuth cannot complete, because the callback is a loopback URL only a browser on the same machine can open. Use the API-token form and feed the token on **stdin**: ```bash echo "$ATLASSIAN_API_TOKEN" | acli jira auth login \ --site "<site>.atlassian.net" --email "<you>@example.com" --token ``` `acli` stores profiles *and* credentials under `~/.config/acli`, so wherever that directory persists, one login serves every later session. - **Never pass a token as a command-line argument.** It lands in shell history and in the process list. Pipe it on stdin as above, never echo it back into the conversation, and never write it to a file in the repository. > **Note:** `acli` has no global `--site`/`-