A maker wants Hermes to hand bug fixes to Codex CLI
The workflow would let Hermes react to bug emails, check Sentry, try to fix the issue, and open a . The coding work should run through Codex CLI, Codex 5.4, and an existing set of personal skills and tools, because that setup is already trusted for code quality.
The main problem is how Hermes can hand work to another tool or model in a reliable way. acpx was tried one or two months earlier, but it was unstable and eventually stopped working.
The current experiment is a that calls Codex CLI directly with a command like `codex exec ...`. The practical need is advice from people running real products with external users, where this kind of handoff has to be dependable.
Key points
- Hermes would receive bug emails and check Sentry for the related issue.
- The actual coding should be done by Codex CLI with the maker’s existing skills and tools.
- acpx was tested before but proved too flaky to rely on.
- A new may call Codex CLI directly using `codex exec ...`.
- The open question is whether anyone has a robust setup for real products with external users.