"On September 9, 2025, the creation of app passwords will be discontinued"

[MrJJ]

We use app password now to allow a git client (git cola) inside a VM with linux to access our repos on Bitbucket.  It's easy to set up and manage.

However, this annoying message that comes with all pushes (spam-ish) suggests it will stop working in some months.

What do I need to do to replace app password with those Api tokens  for use with git ?

We do not want SSH, as it is complicated to set up and maintain. 

AppPassword just worked.  Can I create a new such "App token "and use it in the same manner as App passwords or its nothing like that?  It's not clear what it is, except that it can be used for scripts like curl.  I

[Vitalii Rybka · Accepted solution]

Hey MrJJ! API tokens can work just like app passwords for git, but with a few changes.

What you need: Create a "Repository Access Token" (not regular API token) in your repo settings > Access tokens. Give it "Repositories: Write" permission.

How to use: Same as app passwords - your Bitbucket username + the token as password in git cola.

The downside: Unlike app passwords that worked everywhere, these are per-repository. If you use multiple repos, you'll need separate tokens for each.

Alternatively, you can create workspace access tokens that work across multiple repos in a workspace, but that's slightly more setup.

The actual git workflow stays exactly the same though, so git cola will work identically to how it does now.

[MrJJ]

I tried to make such token and i noticed the last step i was missing was the

git config user.email xxxxx@bots.bitbucket.org to be allowed to write changes back. 

Also I didnt notice its per repro but now that i know it all makes more sense. Like always :) 

Thank you. 

Basically, just make a Token and all is explained on the actual page where you get you token.