Automation

Personal Access Tokens

A Personal Access Token is a long random string that stands in for your password. You use it to push over HTTPS, to call the REST API, and to connect the MCP — without ever handing over your real password.

What it's for

One token, three jobs:

  • Git over HTTPS — when git push or git clone asks for a password, you paste the token instead. See Getting started.
  • The REST API — sent on every request as an Authorization header. See the API reference.
  • The MCP phone line — set as KONNOS_TOKEN so your agent can act as you. See the MCP.

Create a token

  1. 1

    Open your account settings

    Go to Settings and find the Access Tokens section.

  2. 2

    Name it and create

    Give the token a name that tells you what it's for (e.g. laptop or ci) so you can tell your tokens apart later.

  3. 3

    Copy it now — it's shown once

    konnos shows the secret exactly once, right after you create it. Copy it somewhere safe immediately. If you lose it, you can't view it again — you just make a new one.

Using it with git

When git prompts for a password over HTTPS, paste the token:

Username: <you>
Password: <paste your token>

Classic vs fine-grained

Classic

Full account power. Create under Developer → Tokens (classic). Best for your laptop or a trusted automation that needs everything.

Fine-grained

Optional expiry, repository allow-list, and read/write intent. Create under Developer → Fine-grained tokens. Use when a project should only touch selected repos.

Revoke a token

If a token leaks, or you're done with it, revoke it from the same tokens page where you created it. That stops the secret working everywhere without touching your other tokens.

Secrets are shown once

konnos never re-shows a token secret after you leave the create screen. Store it in a password manager or secret store. If you lose it, mint a new token and revoke the old one.