codex-deepseek-subagent

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Codex DeepSeek 子 Agent

Codex DeepSeek Sub-Agent

本 Skill 只维护配置，不承接日常用户任务。确定性的文件、模型目录和凭据操作交给

scripts/codex_deepseek.py

；不要手动改 TOML、JSON、Agent 文件或系统凭据库。

This Skill only maintains configurations and does not undertake daily user tasks. Deterministic operations on files, model directories, and credentials are handled by

scripts/codex_deepseek.py

; do not manually modify TOML, JSON, Agent files, or the system credential store.

关键契约

Key Contracts

只使用桌面应用内置的 Codex 运行时；版本仅用于诊断，兼容性以真实派发验收为准。
从桌面配置读取父模型，并由管理程序应用 v1 明文派发设置；不要硬编码父模型或手改配置。技术原因见 references/compatibility.md。
父模型变化后必须运行
```
repair
```
，再重新验收。
DeepSeek 是纯文本 Agent，不处理图片、视频、截图或其他视觉输入。父 Agent 先识别视觉内容，再传入文字事实。
日常任务只能直接调用：
text
```
spawn_agent(agent_type="DeepSeek", fork_turns="none", ...)
```
不要为日常任务运行本 Skill、管理脚本或
```
codex exec
```
。
当前工具若不认识
```
DeepSeek
```
角色，只提示用户打开新任务或重启 Codex；不得改用默认角色、脚本或
```
codex exec
```
代做当前任务。

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

运行
```
status --json
```
，根据结构化状态继续，不靠文件名猜测。
配置请求运行
```
setup --json
```
；父模型已变化或配置损坏时运行
```
repair --json
```
。
缺少凭据时简洁索要 API Key。收到后不要复述、回显或写入临时文件，只通过
```
--api-key-stdin
```
的标准输入传递。
```
setup
```
或
```
test
```
使用桌面内置运行时创建隔离验收会话。若返回
```
new_task_required
```
或
```
restart_required
```
，提示用户重启桌面应用并打开新任务。
验收必须检查子线程数据库
```
threads
```
表的实际元数据，并确认子 Agent 返回口令
```
NATIVE_DEEPSEEK_OK
```
。两者缺一不可，不能以子 Agent 自述代替。
最终只汇报状态、实际 Provider、模型、思考程度、角色和备份位置；不要输出密钥或原始事件日志。

Run
```
status --json
```
and proceed based on structured status, do not guess by file names.
Run
```
setup --json
```
for configuration requests; run
```
repair --json
```
when the parent model has changed or the configuration is damaged.
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
```
.
```
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.
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.
Finally, only report the status, actual Provider, model, thinking level, role, and backup location; do not output keys or raw event logs.

管理命令

Management Commands

入口。macOS 使用

python3

，Windows 使用

py -3

：

text

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

```
status
```
：只读检查桌面内置运行时、配置、模型目录、凭据和客户端能力。
```
setup
```
：写入配置并验收；缺少密钥时返回
```
credential_missing
```
。
```
test
```
：通过桌面内置运行时执行一次直连测试和一次原生
```
spawn_agent(agent_type="DeepSeek")
```
验收。
```
repair
```
：按当前父模型重新应用配置并验收。
```
disable
```
：停用本 Skill 创建的角色，保留 Provider、模型目录和凭据。
```
uninstall
```
：移除本 Skill 管理的配置；只有用户明确要求删除凭据时才传
```
--remove-credential
```
。

默认使用当前

CODEX_HOME

；仅在用户明确指定其他 Codex Home 时传

--codex-home

。

Entry. Use

python3

for macOS,

py -3

for Windows:

text

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.

By default, use the current

CODEX_HOME

; only pass

--codex-home

when the user explicitly specifies another Codex Home.

状态处理

Status Handling

```
ready
```
：直连、原生路由、数据库元数据和返回口令均通过。
```
configured
```
：静态配置完整，但尚未完成实时验收。
```
credential_missing
```
：索要 API Key 后继续原流程。
```
operation_in_progress
```
：已有配置操作正在运行，稍后重试，不并发修改。
```
conflict
```
：报告冲突文件和字段，等待用户决定是否替换。
```
unsupported
```
：报告缺少的系统能力，不按固定版本号猜测兼容性，也不手工绕过。
```
failed
```
：读取结构化
```
errors
```
；若程序已回滚，明确说明，不再手改配置。

更详细的路径、版本和安全边界见 references/compatibility.md。

```
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.

For more detailed paths, versions, and security boundaries, see references/compatibility.md.