Use Hermes for planning and Claude Code for coding
A practical workflow pairs Hermes with as the main planning system and Claude Code as the coding workspace. In this setup, Hermes and Codex handle planning, research, , long reasoning, tool use, and coordination. Claude Code handles the hands-on work: editing files, code, and moving around the .
The main workflow question is how to pass work from Hermes to Claude Code. The handoff can be manual, by copying plans and specs, or automated through a skill or from Hermes to Claude Code. management is another key concern when using Codex-backed models through OAuth.
The setup may need explicit context_length values in instead of relying only on automatic detection. Long Hermes threads can be ended by asking for dense design docs or specs, then starting a fresh thread with only those summaries. File-reading tools like read_file and long logs also need limits so they do not fill the too quickly.
Key points
- Use Hermes with for planning, research, , and coordination.
- Use Claude Code for file edits, refactors, and navigation.
- Move plans from Hermes to Claude Code manually at first, or later with a skill or .
- Check whether context_length should be set directly in .
- Compress long threads into design docs or specs before starting a fresh thread.