FAQ

A roundup of questions that keep coming up in user channels and issues. If yours isn't here, run /issue from inside AtomCode to file one, or open it on the AtomGit repository.

Install & launch

The install script fails or times out

The one-click installer pulls the binary from GitCode releases by default. If the network blocks it:

• Download the archive for your platform manually from the releases page and drop atomcode onto your PATH;
• or build from source: cargo install --path crates/atomcode (requires Rust 1.80+).

Running atomcode says "command not found"

The install directory isn't on your PATH. The default location is ~/.atomcode/bin — add it to your shell rc file:

export PATH="$HOME/.atomcode/bin:$PATH"

macOS says "cannot be opened because the developer cannot be verified"

Either click "Open Anyway" under System Settings → Privacy & Security, or run:

xattr -d com.apple.quarantine $(which atomcode)

Login & models

The browser doesn't open during OAuth login

Check whether you're on a remote server without a desktop session. For remote environments, prefer API-key login (see Login Methods), or finish OAuth locally and copy ~/.atomcode/auth.json to the same path on the server.

Can't reach the model / hangs forever / timeouts

• First check that base_url in ~/.atomcode/config.toml is reachable — curl the matching /v1/models endpoint;
• On corporate networks it's usually a proxy issue — set HTTPS_PROXY and retry;
• If you're in mainland China hitting an overseas model, verify your egress network. You can run /model to switch to AtomGit's official channel first to prove the whole pipeline works.

How do I switch models?

Inside a session, just type /model and pick from the menu. To persist the choice, edit the model field in ~/.atomcode/config.toml. See Configuration.

Context overflow / "context length exceeded"

• Run /compact to have the model summarise the conversation so far and keep going;
• or /clear to wipe the current context and start over (history is kept as a session — you can /resume at any time);
• Avoid pasting a whole giant file into a prompt; let AtomCode use its file tools to read what it needs.

Permissions & safety

Confirming every command gets annoying

That's the default safety policy. You can:

• Allow ad-hoc: pick "Always allow this kind of action" in the confirmation prompt;
• Allow via config: add commands to the [permissions] allowlist in config.toml.

Where does AtomCode send my code?

Only to the model endpoint you've configured in config.toml. Project files are read locally by tools and shipped as part of the prompt; AtomCode itself does not upload or telemeter code content.

Can I disable specific tools?

Yes — under [tools] in config.toml, set disabled = ["shell", "web_fetch"] to block tools you don't want the model to use.

Usage & interaction

How do I point it at a specific file?

Type @ in the input to trigger file completion, e.g. walk me through @src/main.rs entry logic. You can also just describe the path and the tool will call read_file on its own.

How do I enter a multiline prompt?

Shift+Enter, Alt+Enter, or Ctrl+Enter insert a newline; Enter sends. Full reference at Keybindings.

How do I roll back a bad edit?

Run /undo to revert the file changes produced by the last tool turn. See Sessions & Undo.

Can I resume the previous session?

Yes. Launch with --continue (or -c) to pick up the last session, or run /resume from inside a new session and pick one from the history list.

Skills & project instructions

My skill doesn't show up in the menu

• Check the path: globally ~/.atomcode/skills/<name>/SKILL.md, per-project .atomcode/skills/<name>/SKILL.md;
• Check the frontmatter: both name and description are required;
• Restart atomcode or run /reload to rescan.

What's the difference between .atomcode.md and a skill?

The former is an "always on" project-level convention; the latter is an explicitly invoked workflow. See Skills · Versus project instructions.

Troubleshooting

When filing an issue, please include

• The output of atomcode --version;
• Your OS and architecture;
• Minimal repro steps for the error;
• Relevant logs (redact your API key).

Next steps

• Back to overview
• Quickstart — install from scratch
• Configuration — every adjustable option