Cannot clone Bitbucket repository: Use API token with scopes for authentication

Problem

Cloning a private Bitbucket Cloud repository fails. The IDE prompts for credentials, but Bitbucket no longer permits creating new app passwords, leaving no clear authentication option.

Cause

Bitbucket Cloud has deprecated app passwords and replaced them with API tokens. Two API token formats exist:

• API token with scopes — accepted for Git authentication.
• Regular API token (no scopes) — not accepted for Git authentication.

The IDE delegates authentication to Git, so any credential that works from the command line works in the IDE the same way.

Resolution

1. Generate a Bitbucket API token with scopes that grants repository read/write access. See the Bitbucket Cloud documentation for token generation instructions.
2. From the IDE Welcome screen, click Clone Repository. Inside an open project, use File | Project from Version Control or Git | Clone.
3. Paste the Bitbucket repository URL and click Clone.
4. When prompted for credentials, enter:
   • Username: The Bitbucket account username.
   • Password: The API token with scopes generated in step 1.

Additional Information

A regular Bitbucket API token (without scopes) fails authentication regardless of whether it is used from the IDE or from the command line via git clone. Verify the token type before reporting authentication issues.