独立运营 · 不出售排名位置  · 我们怎么评估工具 →
Anclum 提交收录
5

5o1/DraTamer

本站为独立目录,非该工具官网;下方信息取自其公开仓库。

A Claude-Orchestrated Codex Harness (原文为英文)

装之前:命令归属未核实,仅作参考展示 · 许可证 MIT · 链接可访问

第一步(仅参考,归属未核实):git clone https://github.com/5o1/DraTamer.git

更新 2026-11-17
在 GitHub 查看 ↗链接已于 2026-11-17 核查 · HTTP 200 · 打开的是厂商自己的官网
★ 数取值
0 ★ · 5o1/DraTamer · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
来源明细
从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
收录与活跃
收录于 2026-11-15 · 最近见到 2026-11-20 · 共见到 6 次 · 被 1 个来源列出
评分构成
综合分 103 · 1 个来源 · repo
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 5o1/DraTamer;我们收录于 2026-11-15;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
README 原文(英文,未翻译) · 在 GitHub 读完整 README →

# DraTamer

以下摘录自该仓库的 README(片段)

The white-haired dragon girl should be whipped hard by the orange-haired young lady until she gets to work.
DraTamer is a Claude Code skill for having Claude orchestrate the OpenAI Codex CLI. Claude writes the task, Codex runs in the background, and Claude supervises from Codex's log. When Codex goes off track, Claude stops it and resumes the same session with a written ruling.
## Why
Left alone, Codex tends to:
simplify the task: hardcoding values, skipping checks, swapping in weaker methods;
drift off scope: extra tooling, starting later phases, editing files it should not touch.
Watching it turn by turn is expensive, though. DraTamer keeps the human out of the loop for routine progress and wakes Claude only when something happens.
## How it works
0. Decouple. Claude splits the work by write set (the files, output directories and runtime resources each part changes). Parts with disjoint write sets run as parallel Codex sessions, each with its own task, log and monitor. Parts that edit the same code stay in one session. A new request that doesn't touch a running session's files starts a new session instead of interrupting it.
1. Brief. Claude writes a task file with:
verified context;
a precise method;
critical gates, which stop the run, and non-critical gates, which are recorded and the run continues;
a bounded self-fix budget;
the files Codex may touch, and the files other running sessions own;
the required deliverables.
2. Launch. codex exec runs in the background with an explicit model, sandbox and network setting.
3. Watch. scripts/codex_watch.sh tails the Codex log under Claude Code's Monitor tool. Each output line is an event that wakes Claude:
| Event | Meaning | Throttled |
| CODEX_MSG | Codex wrote an agent message | no |
| CODEX_MSG [after context compaction] | the first message after Codex compacted its context; re-check it against the brief | no |
| CODEX_IDLE | nothing happened for the idle interval (default 15 min) | no |
| CODEX_EXITED | the Codex process is gone | no |
| CODEX_ERROR | a Codex CLI error other than a network error | yes |
| NET_PROBLEM / NET_RECOVERED | network trouble outlasted the tolerance period / ended | yes |
| REMOTE_SSH_FAIL | an ssh connect or key-auth failure in command output | yes |
Each known failure has its own hook, so a real failure does not wait for the idle check. Throttled alerts share a cooldown (WATCH_COOLDOWN, default 30 s): at most one wakes Claude per cooldown. The rest are summarised in a single ALERT_SUPPRESSED line.
Brief network trouble needs no action, because Codex reconnects on its own. API reconnects, websocket/TLS errors and an unreachable backend open a silent tolerance period that closes as soon as the backend answers again. Only trouble lasting longer than WATCH_OUTAGE seconds (default 300) wakes Claude.
4. Intervene. For a change inside the session's own scope, Claude stops Codex, writes a ruling (root cause, corrected method, what stays unchanged), and resumes the same Codex session. Separate new work goes to a parallel session.
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/zh/s/5o1-dratamer/)
来源
github · https://github.com/5o1/DraTamer
按领域浏览
开源项目
收录于
今天

更多条目

全部 1,875 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引