Claude Code — Delegate coding to Claude Code CLI (features, PRs)
Claude Code — Delegate coding to Claude Code CLI (features, PRs)
Start with meaning, then move to detail.
This lesson explains Claude Code — Delegate coding to Claude Code CLI (features, PRs) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Prerequisites, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Claude Code — Delegate coding to Claude Code CLI (features, PRs) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Delegate coding to Claude Code CLI (features, PRs)
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Prerequisites
Read this after the foundation, then connect it to the previous step.
- 04Two Orchestration Modes
Read this after the foundation, then connect it to the previous step.
- 05Mode 1: Print Mode (-p) — Non-Interactive (PREFERRED for most tasks)
Read this after the foundation, then connect it to the previous step.
- 06Mode 2: Interactive PTY via tmux — Multi-Turn Sessions
Read this after the foundation, then connect it to the previous step.
- 07PTY Dialog Handling (CRITICAL for Interactive Mode)
Read this after the foundation, then connect it to the previous step.
- 08Dialog 1: Workspace Trust (first visit to a directory)
Read this after the foundation, then connect it to the previous step.
- 09Dialog 2: Bypass Permissions Warning (only with --dangerously-skip-permissions)
Read this after the foundation, then connect it to the previous step.
- 10Robust Dialog Handling Pattern
Finish here to verify the result and special cases.
Copy only after you understand the effect.
terminal(command="claude -p 'Add error handling to all API calls in src/' --allowedTools 'Read,Edit' --max-turns 10", workdir="/path/to/project", timeout=120)# Start a tmux session
terminal(command="tmux new-session -d -s claude-work -x 140 -y 40")
# Launch Claude Code inside it
terminal(command="tmux send-keys -t claude-work 'cd /path/to/project && claude' Enter")
# Wait for startup, then send your task
# (after ~3-5 seconds for the welcome screen)
terminal(command="sleep 5 && tmux send-keys -t claude-work 'Refactor the auth module to use JWT tokens' Enter")
# Monitor progress by capturing the pane
terminal(command="sleep 15 && tmux capture-pane -t claude-work -p -S -50")
# Send follow-up tasks
terminal(command="tmux send-keys -t claude-work '❯ 1. Yes, I trust this folder ← DEFAULT (just press Enter)
2. No, exitRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.