Remove legacy Codex token env references

Author: austinkennethtucker

AGENTS.md

@@ -26,8 +26,7 @@ Do not bake credentials into the image or Compose files.
 - Docker Hub auth belongs in local Docker credential storage via `docker login`.
 - The wrapper bearer token belongs in `data/secrets/proxy_api_key`.
 - Codex/ChatGPT auth belongs in the dedicated bind-mounted `data/codex-home`.
-- Do not use or add `OPENAI_API_KEY`, `CODEX_API_KEY`, or
-  `CODEX_ACCESS_TOKEN` for this project.
+- Do not use or add `OPENAI_API_KEY` for this project.
 
 Codex login is completed inside the running container so credentials are written
 to the mounted `/root/.codex` backed by `data/codex-home`:

README.md

@@ -19,13 +19,10 @@ that login is allowed by the applicable OpenAI product terms and policies. This
 repository does not grant permission to power third-party integrations with a
 ChatGPT subscription.
 
-The service deliberately refuses startup when API-key environment variables are
-present:
+The service deliberately refuses startup when `OPENAI_API_KEY` is present:
 
 ```text
 OPENAI_API_KEY
-CODEX_API_KEY
-CODEX_ACCESS_TOKEN
 ```
 
 Codex authentication belongs only in the dedicated bind-mounted
@@ -170,9 +167,9 @@ Check readiness:
 curl -sS http://127.0.0.1:8320/healthz
 ```
 
-`/healthz` returns 200 only after the container sees the pinned Codex CLI, a
-dedicated ChatGPT login, and no API-key mode. It is normal for the container to
-report unhealthy before device login is complete.
+`/healthz` returns 200 only after the container sees the pinned Codex CLI and a
+dedicated ChatGPT login. It is normal for the container to report unhealthy
+before device login is complete.
 
 ## API Examples
 
@@ -292,8 +289,8 @@ docker compose -f docker-compose.image.yml up -d
 ```
 
 Docker registry authentication belongs in local Docker credential storage via
-`docker login`. Do not put Docker Hub passwords, ChatGPT/Codex credentials,
-OpenAI API keys, or Codex access tokens in Compose files.
+`docker login`. Do not put Docker Hub passwords, ChatGPT/Codex credentials, or
+OpenAI API keys in Compose files.
 
 Codex authentication still lives only in the mounted `data/codex-home`
 directory and must be completed inside the running container.
@@ -371,8 +368,7 @@ docker compose restart
 - `502` or `/healthz` returning `503`: check
   `docker exec -it codex-cli-provider codex login status`, then re-run device
   login if needed.
-- Accidental API-key detection: unset `OPENAI_API_KEY`, `CODEX_API_KEY`, and
-  `CODEX_ACCESS_TOKEN` before starting.
+- Accidental API-key detection: unset `OPENAI_API_KEY` before starting.
 - Sandbox failure: this configuration intentionally uses Codex
   `danger-full-access` inside Docker. Do not add `privileged`, `SYS_ADMIN`,
   unconfined seccomp/AppArmor, host networking, or host home mounts.

docs/discovery.md

@@ -61,8 +61,7 @@ The official repository README says each archive contains a single platform-name
 - Browser login can fail in headless environments; OpenAI docs recommend device-code auth first.
 - File-backed ChatGPT sessions refresh tokens automatically during use, so the dedicated `CODEX_HOME` must be writable if token refresh is required.
 - Official docs describe copying `auth.json` for headless/CI workflows, but this project must not copy a normal user `~/.codex`; any login flow must use a dedicated project auth home.
-- `CODEX_API_KEY` is supported by `codex exec`; this project must refuse API-key mode.
-- `CODEX_ACCESS_TOKEN` is documented for trusted automation but must not be used by this adapter.
+- This project uses only device-based ChatGPT login in the dedicated project auth home.
 
 ## Tool And Persistence Controls
 

scripts/check_compose_security.py

@@ -7,7 +7,7 @@
 from typing import Any
 
 
-FORBIDDEN_ENV = {"OPENAI_API_KEY", "CODEX_API_KEY", "CODEX_ACCESS_TOKEN"}
+FORBIDDEN_ENV = {"OPENAI_API_KEY"}
 
 
 def fail(message: str) -> None:
@@ -118,7 +118,7 @@ def main() -> None:
     env = service.get("environment") or {}
     env_names = set(env if isinstance(env, dict) else [])
     if FORBIDDEN_ENV.intersection(env_names):
-        fail("API-key environment variables must not be set in compose")
+        fail("OPENAI_API_KEY must not be set in compose")
 
     tmpfs = {str(item).split(":", 1)[0] for item in as_list(service.get("tmpfs"))}
     if "/tmp" not in tmpfs:

src/codex_runner.py

@@ -15,7 +15,7 @@
 DEFAULT_WORK_DIR = "/workspace"
 STDERR_LIMIT = 64_000
 STDOUT_LIMIT = 256_000
-FORBIDDEN_ENV_VARS = ("OPENAI_API_KEY", "CODEX_API_KEY", "CODEX_ACCESS_TOKEN")
+FORBIDDEN_ENV_VARS = ("OPENAI_API_KEY",)
 FORBIDDEN_EVENT_FRAGMENTS = (
     "exec_command",
     "shell",
@@ -59,7 +59,7 @@ def from_env(cls, default_model: str | None, request_timeout_seconds: int) -> "R
 def fail_if_api_key_environment() -> None:
     present = [name for name in FORBIDDEN_ENV_VARS if os.environ.get(name)]
     if present:
-        raise RuntimeError("API-key or access-token environment variables are not allowed")
+        raise RuntimeError("OPENAI_API_KEY is not allowed")
 
 
 def build_child_env(codex_home: str, child_home: str) -> dict[str, str]:

src/server.py

@@ -17,7 +17,6 @@
 from fastapi.responses import FileResponse, JSONResponse, RedirectResponse, Response, StreamingResponse
 
 from src.codex_runner import (
-    FORBIDDEN_ENV_VARS,
     LocalCodexRunner,
     RunnerError,
     build_child_env,

tests/test_server.py

@@ -573,14 +573,6 @@ def test_api_key_environment_causes_startup_refusal(monkeypatch):
         AppSettings.from_env()
 
 
-@pytest.mark.parametrize("name", ["CODEX_API_KEY", "CODEX_ACCESS_TOKEN"])
-def test_other_api_key_environments_cause_startup_refusal(monkeypatch, name):
-    monkeypatch.delenv("OPENAI_API_KEY", raising=False)
-    monkeypatch.setenv(name, "not-allowed")
-    with pytest.raises(RuntimeError):
-        AppSettings.from_env()
-
-
 def test_weak_proxy_secret_causes_startup_refusal(monkeypatch):
     monkeypatch.delenv("OPENAI_API_KEY", raising=False)
     monkeypatch.setenv("PROXY_API_KEY", "change-me")