Login Methods

AtomCode supports two ways to connect to an LLM: AtomGit CodingPlan (with free tokens) and traditional API keys. This page helps you pick the right path and walks through the binding.

Two methods at a glance

As of v4.25.0 /codingplan has been folded into /login; the previous "OAuth-only without claiming tokens" entry has been removed.

AtomGit CodingPlan (recommended)

AtomGit is the open-source code-hosting platform run by CSDN / OpenAtom Open Source Foundation, and AtomCode natively integrates its OAuth and CodingPlan. /login is the lowest-friction entry point for new users: a single action logs you in → claims free token quota → auto-generates a provider config from the granted model list. After that one command you can start chatting immediately. Re-running it after you're already signed in idempotently re-syncs the model list — no double-claim.

CodingPlan tier system

CodingPlan currently offers three tiers. The system automatically grants the highest tier you're eligible for. Quota is measured on a rolling 5-hour window:

After claiming Pro or above, run /login in AtomCode to sync the updated model list. For details, visit the CodingPlan page.

From the first-run wizard

1. The first time you run atomcode, the 3-step wizard pops up automatically.
2. Step 1 (welcome): press Enter. Step 2 (language): press 1 / 2 / 3 to pick.
3. Step 3 (setup): pick One-click with AtomGit CodingPlan (option 1).
4. The browser opens the AtomGit authorization page — click Allow.
5. After authorization, the TUI claims CodingPlan and writes the provider config. No need to touch config.toml — start sending messages.

If you skipped earlier and want to redo the wizard, run /welcome any time.

From an existing session

Once inside the TUI, run:

/login

The browser opens to complete authorization, claim CodingPlan, and refresh the provider list. Running it again re-syncs the model list — the local AtomGit* providers are updated to the latest entitled models.

From the command line

atomcode login

Useful in scripts, remote servers, or container images for a one-shot setup. The CLI subcommand and the TUI /login share the same flow and emit the same report. Note: atomcode codingplan is kept as a hidden alias so existing scripts and muscle memory don't break after the fold.

Check status / log out

atomcode status     # or /status in the TUI — includes CodingPlan usage and expiry
atomcode logout     # or /logout in the TUI — clears the OAuth token

API key method

To use your own OpenAI / Claude / DeepSeek / GLM key, there are three ways:

Option A: /provider in the TUI

1. Type /provider in the TUI.
2. Choose a vendor preset or a custom account, enter its API key, then add one or more models under that account.
3. The configuration is written back to ~/.atomcode/config.toml.

Option B: hand-edit the config file

Edit ~/.atomcode/config.toml directly and add a [providers.*] entry; see ProviderConfig fields.

Option C: one-shot CLI override

Don't want to touch the config file and only need a different provider for one run? Add flags at launch:

atomcode --provider deepseek --model deepseek-reasoner

Which one should I pick?

• First-time user → CodingPlan (/login) — free tokens, just use it.
• Already have your own API key → skip /login and use the API key path (/provider or hand-edit config). If you later need the built-in AtomGit repository, PR, or Issue tools, run /login to authorize them; this also claims CodingPlan and registers AtomGit-* providers.
• Running in CI / scripts → API key via config file or env vars.
• Fully offline → configure an Ollama provider — no login required.

Next steps

• Basic Usage — first thing after logging in: learn how to phrase tasks.
• Slash Commands — /provider, /model, /status in detail.