Hermes as a Coding Agent
Source: r/hermesagent community discussion (May 2026) Based on: "Hermes as a Coding Agent???" thread (33 comments) + multiple workflow discussions
Can Hermes Be a Coding Agent?
Yes. The community actively uses Hermes for coding, with several established patterns. However, it's not a drop-in replacement for dedicated coding agents like OpenCode or KiloCode without some setup.
u/Rheath72's question: "I know a lot of the examples show Hermes as a coding agent and I don't fully grasp it yet."
Why Use Hermes for Coding vs Dedicated Tools?
Advantages of Hermes
- Chat-based interface - Code from any device, including mobile (u/Xiaomin4114: "the biggest use-case is it sits in chat. So you can do code from any device, or in teams, or while on the toilet")
- Self-improving system - Builds workflow-specific skills over time
- Less repetitive context - No need to re-explain project on every session
- Multi-tool access - Terminal, file editing, web browsing, git all available
When Dedicated Agents Are Better (u/An-R-Nguyen)
- Clear checkpoints, backlog, tickets, large codebase -> OpenCode is better for isolating tasks and refactoring
- Gradually building stuff, aiming for velocity -> Hermes is good due to self-improve system
Coding Workflow Patterns
Pattern 1: Dedicated Coder Profile (u/An-R-Nguyen)
Setup:
- Main profile: Orchestrator - takes requests, plans, QC gates
- Coder profile: One-shots coding requests with one job
Workflow:
- Main profile receives coding request
- Delegates to coder profile
- Coder aims for 80%+ quality pass in single shot
- If quality < 80%, main profile nukes work and starts over rather than fixing
Rationale: "When a job is not one shotted and have at least 80% quality pass, not worth the effort fixing it. Best to just start over."
Pattern 2: Autonomous VPS Development (u/An-R-Nguyen)
- Rent dedicated VPS for coding agent
- Agent has full terminal access, can install dependencies
- Works autonomously on greenfield projects
- Human reviews and merges when ready
Best for: Greenfield projects where velocity matters more than incremental review
Pattern 3: GitHub Integration Pipeline (u/Xiaomin4114)
Full workflow:
- Create separate GitHub account for Hermes
- Generate SSH key, add pubkey to GitHub account
- Share repos with bot account
- Hermes pushes code as bot's commits
- Human reviews PRs and merges to main
Advanced automation:
- "Hey, check server logs in last 5 minutes" -> finds error -> correlates to code -> makes PR
- Human checks and merges
- "OK, pull and deploy" -> agent deploys automatically
Pattern 4: Per-Class/Per-Method Approach (u/Stitch10925)
For larger projects:
- Break work into per-class or per-method tasks
- Smaller scope = higher quality single shots
- Orchestrator ensures everything fits together
- Requires more user intervention for coordination
Security Setup for Coding
GitHub Access Pattern (u/Xiaomin4114)
DO:
- Create separate GitHub account for Hermes
- Generate dedicated SSH key pair
- Share repos with bot account (don't give direct access to main account)
- Stage changes, human pushes (or approve PRs before merge)
DON'T:
- Give Hermes your personal GitHub credentials
- Allow unrestricted push to main branch without review
- Share sensitive repo access
File System Boundaries
Set in SOUL.md or AGENTS.md:
Coding boundaries:
- Only modify files within /path/to/project/
- Do NOT modify system files or ~/.hermes configuration
- Stage changes, do not push without explicit approval
- Always create git commits with descriptive messages
Model Recommendations for Coding
Best Models for Coding Tasks
| Model | Strengths | Best For |
|---|---|---|
| Qwen 3.6-27B (local vLLM) | Excellent tool calling, fast iteration | Daily coding work |
| Qwen 3.6-35B | Better reasoning for complex architecture | Complex projects |
| Claude (via OpenRouter) | Strong code generation quality | Code review, planning |
| GPT-5.5 | High capability, reliable | Complex debugging |
Community Consensus
- Qwen 3.6 variants are the go-to for coding with Hermes
- Use stronger models (Claude/GPT) for planning and review phases
- Local vLLM deployment gives best performance/iteration speed
Language-Specific Notes
.NET / C#
u/Stitch10925 reported difficulty accomplishing anything with Hermes in .NET on 16GB VRAM. May be model/setup dependent rather than language-specific limitation.
Python
Widely tested and confirmed working well. Most community examples use Python projects.
JavaScript/TypeScript
Commonly used for web projects, no specific issues reported.
Common Coding Agent Issues
Hermes Edits Its Own Code (u/insidesliderspin)
Issue: Agent edited gateway platform Python files to "fix" bugs it thought it found.
Solution: Set explicit boundaries in SOUL.md about which directories are off-limits. Use git for version control so you can revert unwanted changes.
Context Loss During Long Coding Sessions
Issue: After multiple context compactions, Hermes loses the thread on large projects.
Solution (u/trashacct383): Maintain project plan document and state file in persistent directory to track progress across sessions.
Getting Started with Coding on Hermes
- Create a dedicated coding profile with focused SOUL.md
- Set up GitHub integration with separate bot account
- Define file system boundaries clearly
- Start with small projects - scripts, utilities, simple web apps
- Use the plan-execute-QC loop for anything non-trivial
- Keep git commits frequent and descriptive
Comparison with Other Coding Agents
| Feature | Hermes | OpenCode | KiloCode |
|---|---|---|---|
| Chat interface (any device) | Yes | Limited | Limited |
| Self-improving skills | Yes | No | No |
| Multi-tool access | Terminal, web, files | Primarily code | Primarily code |
| Best for isolated tasks | Good | Excellent | Excellent |
| Best for velocity/greenfield | Excellent | Good | Good |
| Large codebase refactoring | Moderate | Excellent | Excellent |
Community verdict: Use Hermes when you want chat-based access, self-improvement, and multi-tool workflows. Use dedicated coding agents for large-scale refactoring and isolated ticket-driven work.