TWG CLI uses a single Atlassian identity (email + API token) for most products. Some products require additional or separate tokens.
1 2twg login
You will be prompted for:
| Prompt | What to enter |
|---|---|
| Site prefix | Your Atlassian site name (e.g. mycompany) |
| Your Atlassian account email | |
| API Token | Generated at id.atlassian.com/manage-profile/security/api-tokens |
Credentials are saved to ~/.twg/auth.conf.
Some products require separate tokens due to different API scoping:
| Product | Auth Method | Setup |
|---|---|---|
| Bitbucket | Separate app password | twg login --product bitbucket |
| Rovo Search | MCP-scoped token | Configured during twg login or via env vars |
| Trello | Trello API key + token | twg login --product trello |
You'll be prompted automatically on first use of any product that requires separate auth.
For CI/CD and scripted use, set environment variables instead of running twg login:
| Variable | Purpose |
|---|---|
TWG_USER | Atlassian account email |
TWG_TOKEN | Atlassian API token |
TWG_SITE | Default site prefix |
TWG_BBC_TOKEN | Bitbucket Cloud app password |
TWG_MCP_TOKEN | Rovo MCP-scoped token |
Rate this page: