hotheat/dsh-claude-codex-mode
Splits DSH work in two: discussion stays read-only, and every code edit inside a Git repository goes to the Codex CLI after you say go.
A division of labour enforced in code rather than by instruction. Discussion — requirements, plans, architecture, docs, reading code, judging whether a fix is worth making — stays read-only. Edits to code or config inside a Git repository go through a bundled MCP server to the Codex CLI, and only after you say go. A write guard blocks the model from writing a repository code file with a structured edit tool and tells it where the edit belongs instead. After the edit, DSH reviews git status, git diff and the test results itself before reporting back, so the claim that something works is checked against the repository rather than asserted.
Install
dsh plugin --profile web add github:hotheat/dsh-claude-codex-modeThe GitHub install line from the README. The bundle has modes — an api mode where the DSH model handles discussion and a claude-code-cli mode that forwards discussion to the Claude Code CLI — and the README says the bundle is designed with Claude in mind, so in api mode you should pick a Claude model as the DSH default.
Compatibility
The README requires DSH >=0.2.1-rc.2 <0.3.0 and Node.js >= 20, with preflight checks: codex --version must succeed in every mode, and claude --version must succeed in claude-code-cli mode. Both are blocking checks, so a missing CLI fails at preflight rather than mid-task.
Details
- Repo: hotheat/dsh-claude-codex-mode
- Category: Workflow & Automation
- Stars: 0
- Version: no npm release; installed from the repository
Alternatives
yzhclcl/dsh-plan-build-mode · snailium/dsh-command-context-trim · Zhiyi-Zhao/dsh-schedule-send