5
5o1/DraTamer
A Claude-Orchestrated Codex Harness
updated 2026-11-17
View on GitHub ↗Link checked 2026-11-17 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · 5o1/DraTamer · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-15 · last seen 2026-11-20 · seen 6× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: Open Source. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
5o1/DraTamer;first catalogued 2026-11-15;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# DraTamer
Excerpted from the repository README (abridged)
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.
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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/5o1-dratamer/)
- Source
- github · https://github.com/5o1/DraTamer
- Browse by field
- Open source
- added
- today
More entries
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.