Access Tokens

To clone or push a repo over HTTPS — especially a private one — you authenticate to the git server with an access token tied to your account.

Generate a token from the website

Open your Profile and use Generate access token. Because the token is a long-lived-ish git credential shown on screen, minting it is protected by an email one-time code (OTP):

1. Click Generate access token.
2. ChipAI.dev emails a 6-digit code to your account address. The code is valid for 10 minutes.
3. Enter the code to reveal your token.

You get 5 attempts per code; after that (or once it expires) request a fresh one. The code is only consumed once a token is actually issued, so a transient error won't burn it — you can retry with the same code.

Why the extra step? The OTP proves control of your inbox before a push credential is revealed in the browser. It applies only to the website's "Generate access token" action.

Using the token with git

git clone https://<username>:<token>@<git-host>/<owner>/<repo>.git
# or let git prompt and paste the token as the password
git clone https://<git-host>/<owner>/<repo>.git

The token grants whatever access your account has on that repo (see Contributors & Roles).

CLI and automation are unaffected

The mind CLI's git credential helper handles automated clone/push without an OTP — only interactive, opt-in web requests are gated. So scripted git operations and CI keep working unattended.

Next: Profile Settings · Contributors & Roles