CLI

Coming soon

A command-line client for Taiga Cloud is in development. This page will carry installation and usage once it is available.

Until then

Nothing about the platform requires a CLI — everything it will do is available over the API today, and the pieces a CLI needs are already in place.

Authenticating from a terminal

The device code flow is built for exactly this: no client registration, no redirect URI, no browser on the machine running the commands. Request a code, approve it wherever you do have a browser, and poll for the token.

# 1. request a code
curl -s -X POST https://api.taigacloud.com/v2/oauth2/device/code \
  -H "Content-Type: application/json" \
  -d '{"device_name": "my-laptop"}'

# 2. open the verification_uri it returns, then poll
curl -s -X POST https://api.taigacloud.com/v2/oauth2/device/token \
  -H "Content-Type: application/json" \
  -d '{"grant_type": "device_code", "device_code": "…"}'

Keep the refresh token and you will not have to approve again for a week.

Scripting against the API

export TOKEN="…"   # access_token.token from the response above

curl -s https://api.taigacloud.com/v2/projects \
  -H "Authorization: Bearer $TOKEN" | jq '.results[] | {id, name}'

Every list endpoint returns the same envelope, so .results works the same way everywhere — see Collections in the reference.

Or generate a client

For anything longer than a few commands, generating a typed client is usually less work than accumulating shell scripts — see SDK.

What a CLI will not change

It will sit on the same API, use the same device flow, and be bound by the same roles. Anything you cannot do through the API today will not become possible through a CLI, and scripts written against the API now will keep working alongside it.