Atom
English

Team & Enterprise AI Setup

Most people only need Atom’s normal sign-in flow. This page is for teams that manage AI access through company accounts, API keys, or enterprise policy.

OpenAI / Codex

Atom includes the Codex runtime, but Codex still reads the normal local Codex account and configuration on the computer.

Use this path if your team uses ChatGPT Business, ChatGPT Enterprise, OpenAI API billing, or managed Codex policy.

  1. Configure Codex on the computer using your team’s standard setup.
  2. Sign in with the company ChatGPT account, or configure the team’s OpenAI API key setup.
  3. If your team uses managed policy, let your admin manage it through OpenAI’s managed requirements, MDM, or system configuration.
  4. Open Atom.

config.toml is useful for local defaults. It is not a replacement for sign-in or API-key setup, and enterprise-managed requirements take priority over local files.

Official docs: Codex managed configuration

OpenCode

OpenCode uses its own local installation and model-provider configuration rather than an OpenAI or Anthropic sign-in managed by Atom.

  1. Install OpenCode using your team’s approved software process.
  2. Configure the company-approved model provider and credentials through OpenCode.
  3. Confirm OpenCode can reach that provider outside Atom.
  4. Choose OpenCode in Atom and click Check again.

Usage, retention, and policy follow the provider configured in OpenCode. Atom does not copy that provider configuration into its own account system.

What Atom does

Atom does not proxy AI traffic, store your provider keys, or add usage fees. Codex usage comes from your OpenAI setup, Claude Code usage comes from Anthropic, and OpenCode usage comes from whichever model provider your team configures locally.