The whole point of the bridge is that the project gets its own CODEX_HOME, so y…

Max Kle1nz@maxkle1nz

The whole point of the bridge is that the project gets its own CODEX_HOME, so your global ChatGPT-account Codex session never leaks into project work. This guard is where that boundary is enforced: no project-local login, no run. The error intentionally prints the two recovery paths (device auth or API key) instead of a generic "not authenticated" — the fix should be copy-pasteable from the failure itself.

ensure_local_codex_auth() {
  ensure_project_dirs
  if CODEX_HOME="$PROJECT_CODEX_HOME" "$CODEX_BIN" login status >/dev/null 2>&1; then
    return 0
  fi

  print_stderr_lines \
    "[omx-bridge] No project-local Codex login found in:" \
    "[omx-bridge]   $PROJECT_CODEX_HOME" \
    "[omx-bridge] To continue, use one of:" \
    "[omx-bridge]   $SELF_NAME codex-login-device" \
    "[omx-bridge]   OPENAI_API_KEY=... $SELF_NAME codex-login-api-key"
  exit 1
}