[Bug]: Codex loged in successfully but Codex start up failed when checking with ds doctor

[VoyagerXvoyagerx]

Summary

PS: 服务器在大陆内，已经开启代理，可以正常使用 Codex

(insam) zkcs@zkcs:/data384/zyj/e2h_codex$ codex login
Starting local login server on http://localhost:1455.
If your browser did not open, navigate to this URL to authenticate:

https://auth.openai.com/oauth/authorize?response_type=code&client_id=app_EMoamEEZ73f0CkXaXp7hrann&redirect_uri=htt....

On a remote or headless machine? Use `codex login --device-auth` instead.
Successfully logged in
(insam) zkcs@zkcs:/data384/zyj/e2h_codex$ ds doctor
DeepScientist doctor

Home: /home/zkcs/DeepScientist
Web UI: http://127.0.0.1:20999
Checked at: 2026-05-05T05:28:02+00:00

[ok] Python runtime: Local Python runtime imports succeeded.

[ok] Home path: DeepScientist home exists and is writable.

[ok] uv runtime manager: uv is available for locked Python runtime management.
  resolved binary: /home/zkcs/.local/bin/uv

[ok] Shell backend: DeepScientist resolved platform shell backends for command and terminal sessions.

[ok] Git: Git is available for quest repositories.

[ok] Config files: Required config files validated successfully.

[warn] Supported runners: Runner policy matches the current release surface.
  warning: `claude` remains a TODO/reserved runner slot and is not runnable yet.

[fail] Codex CLI: Codex startup probe failed.
  error: Codex did not complete the startup hello probe successfully.
  error: Run `codex login` (or just `codex`) once and complete login before starting DeepScientist.
  resolved binary: /home/zkcs/.npm-global/bin/codex

[ok] Recent runtime failures: No recent quest runtime failures were found.

[ok] LaTeX runtime (optional): A local `pdflatex` runtime is available for paper builds.
  pdflatex: /usr/bin/pdflatex

[ok] UI bundles: Web and TUI bundles are present.

[fail] Web port: The configured port is already used by another DeepScientist home.
  error: http://127.0.0.1:20999 is already serving a daemon for `/data384/zyj/e2h_codex/DeepScientist`.
  url: http://127.0.0.1:20999

Next steps

1. Run `codex login` (or just `codex`) in a terminal and complete login or first-run setup.
2. If `codex` is missing, install it explicitly with `npm install -g @openai/codex`.
3. If the configured model is not available to your Codex account, update `~/DeepScientist/config/runners.yaml` and try again.
4. Then run `ds doctor` and start DeepScientist again.
5. Stop the other daemon first or change `ui.port` in `~/DeepScientist/config/config.yaml`.

DeepScientist is not fully ready yet. Fix the failed checks above, then rerun `ds doctor`.

Steps to reproduce

Operation system: Linux

Expected behavior

ds launch successfully

Actual behavior

ds launched and works, but codex login failed

Environment

• DeepScientist v1.5.17
• OS Linux zkcs 5.15.0-78-generic [Bug]: 'QuestService' object has no attribute 'enrich_conversation_message_event' #85-Ubuntu SMP (x86_64)
• Python 3.11.15 (conda-forge, GCC 14.3.0)
• Node v20.19.0

Logs, screenshots, or stack traces

Suspected scope

No response