auth.md Codex Docs, 2026-03-03 00:35 UTC → 2026-05-18 22:01 UTC

20 20 

21When you sign in with ChatGPT from the Codex app, CLI, or IDE Extension, Codex opens a browser window for you to complete the login flow. After you sign in, the browser returns an access token to the CLI or IDE extension.21When you sign in with ChatGPT from the Codex app, CLI, or IDE Extension, Codex opens a browser window for you to complete the login flow. After you sign in, the browser returns an access token to the CLI or IDE extension.

22 22 

23If your environment already provides a ChatGPT access token, the CLI can read

24it from stdin:

25 

26```shell

27printenv CODEX_ACCESS_TOKEN | codex login --with-access-token

28```

29 

23### Sign in with an API key30### Sign in with an API key

24 31 

25You can also sign in to the Codex app, CLI, or IDE Extension with an API key. Get your API key from the [OpenAI dashboard](https://platform.openai.com/api-keys).32You can also sign in to the Codex app, CLI, or IDE Extension with an API key. Get your API key from the [OpenAI dashboard](https://platform.openai.com/api-keys).

26 33 

27OpenAI bills API key usage through your OpenAI Platform account at standard API rates. See the [API pricing page](https://openai.com/api/pricing/).34OpenAI bills API key usage through your OpenAI Platform account at standard API rates. See the [API pricing page](https://openai.com/api/pricing/).

28 35 

29Recommendation is to use API key authentication for programmatic Codex CLI workflows (for example CI/CD jobs). Do not expose Codex execution in untrusted or publicly triggerable environments.36Features that rely on ChatGPT credits, such as [fast mode](https://developers.openai.com/codex/speed), are

37available only when you sign in with ChatGPT. If you sign in with an API key,

38Codex uses standard API pricing instead.

39 

40We recommend API key authentication for programmatic Codex CLI workflows, such

41as CI/CD jobs. Don't expose Codex execution in untrusted or public environments.

42 

43### Use Codex access tokens for enterprise automation

44 

45In ChatGPT Enterprise workspaces, admins can allow permitted members to create

46Codex access tokens for trusted, non-interactive Codex local workflows. Use an

47access token when automation needs ChatGPT workspace access, ChatGPT-managed

48Codex entitlements, or enterprise workspace controls without a browser sign-in.

49 

50Access tokens are intended for trusted scripts, schedulers, and private CI

51runners. For general OpenAI API calls, continue to use Platform API keys.

52 

53For setup steps, permissions, rotation, and revocation guidance, see

54[Access tokens](https://developers.openai.com/codex/enterprise/access-tokens).

30 55 

31## Secure your Codex cloud account56## Secure your Codex cloud account

32 57 

85 110 

86If the active credentials don't match the configured restrictions, Codex logs the user out and exits.111If the active credentials don't match the configured restrictions, Codex logs the user out and exits.

87 112 

88These settings are commonly applied via managed configuration rather than per-user setup. See [Managed configuration](https://developers.openai.com/codex/security#managed-configuration).113These settings are commonly applied via managed configuration rather than per-user setup. See [Managed configuration](https://developers.openai.com/codex/enterprise/managed-configuration).

114 

115## Login diagnostics

116 

117Direct `codex login` runs write a dedicated `codex-login.log` file under

118your configured log directory. Use it when you need to debug browser-login or

119device-code failures, or when support asks for login-specific logs.

120 

121## Custom CA bundles

122 

123If your network uses a corporate TLS proxy or private root CA, set

124`CODEX_CA_CERTIFICATE` to a PEM bundle before logging in. When

125`CODEX_CA_CERTIFICATE` is unset, Codex falls back to `SSL_CERT_FILE`. The same

126custom CA settings apply to login, normal HTTPS requests, and secure WebSocket

127connections.

128 

129```shell

130export CODEX_CA_CERTIFICATE=/path/to/corporate-root-ca.pem

131codex login

132```

89 133 

90## Login on headless devices134## Login on headless devices

91 135 

141docker cp ~/.codex/auth.json MY_CONTAINER:"$CONTAINER_HOME/.codex/auth.json"185docker cp ~/.codex/auth.json MY_CONTAINER:"$CONTAINER_HOME/.codex/auth.json"

142```186```

143 187 

188For a more advanced version of this same pattern on trusted CI/CD runners, see

189[Maintain Codex account auth in CI/CD (advanced)](https://developers.openai.com/codex/auth/ci-cd-auth).

190That guide explains how to let Codex refresh `auth.json` during normal runs and

191then keep the updated file for the next job. API keys are still the recommended

192default for automation.

193 

144### Fallback: Forward the localhost callback over SSH194### Fallback: Forward the localhost callback over SSH

145 195 

146If you can forward ports between your local machine and the remote host, you can use the standard browser-based flow by tunneling Codex's local callback server (default `localhost:1455`).196If you can forward ports between your local machine and the remote host, you can use the standard browser-based flow by tunneling Codex's local callback server (default `localhost:1455`).