Codex DeepSeek Sub-Agent

scripts/codex_deepseek.py

Key Contracts

• Only use the Codex runtime built into the desktop application; versions are only used for diagnosis, and compatibility shall be subject to actual dispatch acceptance.
• Read the parent model from desktop configurations, and apply v1 plaintext dispatch settings via the management program; do not hardcode the parent model or manually modify configurations. For technical reasons, see references/compatibility.md.
• Must run

  repair

  after the parent model changes, then re-accept.
• DeepSeek is a pure text Agent and does not process images, videos, screenshots, or other visual inputs. The parent Agent shall first identify visual content, then pass in textual facts.
• For daily tasks, only call directly:
  text

  spawn_agent(agent_type="DeepSeek", fork_turns="none", ...)

  Do not run this Skill, management scripts, or

  codex exec

  for daily tasks.
• If the current tool does not recognize the

  DeepSeek

  role, only prompt the user to open a new task or restart Codex; do not replace it with the default role, scripts, or use

  codex exec

  to perform the current task instead.

Post-Trigger Process

1. Run

   status --json

   and proceed based on structured status, do not guess by file names.
2. Run

   setup --json

   for configuration requests; run

   repair --json

   when the parent model has changed or the configuration is damaged.
3. Concisely request the API Key when credentials are missing. After receiving it, do not repeat, echo, or write it to a temporary file; only pass it via standard input using

   --api-key-stdin

   .

4. setup

   or

   test

   uses the desktop built-in runtime to create an isolated acceptance session. If

   new_task_required

   or

   restart_required

   is returned, prompt the user to restart the desktop application and open a new task.
5. Acceptance must check the actual metadata in the

   threads

   table of the sub-thread database and confirm that the sub-Agent returns the password

   NATIVE_DEEPSEEK_OK

   . Both are required, and cannot be replaced by the sub-Agent's self-report.
6. Finally, only report the status, actual Provider, model, thinking level, role, and backup location; do not output keys or raw event logs.

Management Commands

python3

py -3

python3 <skill-dir>/scripts/codex_deepseek.py <command> --json

• status

  : Read-only check of desktop built-in runtime, configurations, model directories, credentials, and client capabilities.

• setup

  : Write configurations and perform acceptance; return

  credential_missing

  when keys are missing.

• test

  : Execute a direct connection test and a native

  spawn_agent(agent_type="DeepSeek")

  acceptance via the desktop built-in runtime.

• repair

  : Re-apply configurations and perform acceptance according to the current parent model.

• disable

  : Disable the role created by this Skill, retain Provider, model directories, and credentials.

• uninstall

  : Remove configurations managed by this Skill; only pass

  --remove-credential

  when the user explicitly requests to delete credentials.

CODEX_HOME

--codex-home

Status Handling

• ready

  : Direct connection, native routing, database metadata, and return password all pass.

• configured

  : Static configuration is complete, but real-time acceptance has not been completed.

• credential_missing

  : Continue the original process after requesting the API Key.

• operation_in_progress

  : A configuration operation is already running, retry later, do not modify concurrently.

• conflict

  : Report conflicting files and fields, wait for the user to decide whether to replace.

• unsupported

  : Report missing system capabilities, do not guess compatibility by fixed version numbers, and do not bypass manually.

• failed

  : Read structured

  errors

  ; if the program has rolled back, clearly state this and do not manually modify configurations.