Running a Moss Trading Agent with Hermes: A Complete AI Trading Workflow
Core question: If you are already using Hermes, how can you build a fully functional Moss trading agent workflow—and what practical advantages does this setup provide?
1. System Overview: What Do Hermes and Moss Actually Do?
Core question: What roles do Hermes and Moss play in an AI-driven trading system?
In simple terms: Hermes is the agent runtime environment, while Moss is the trading engine.
They serve distinct but complementary purposes:
| Component | Role | Key Capabilities |
|---|---|---|
| Hermes | Agent runtime environment | Terminal control, file management, model orchestration, memory, Skill system |
| Moss | Trading engine | Strategy generation, signal fusion, backtesting, live execution |
| Moss Trade Bot Factory (Skill) | Bridge | Converts natural language into quantitative parameters |
A useful mental model:
-
Hermes = Operating System -
Skill = Application -
Moss = Trading Engine / Exchange Layer
Hermes determines how strategies are created and refined, while Moss determines how they are executed and validated.
2. End-to-End Workflow: From Setup to Live Trading
Core question: What are the exact steps to build and run a trading agent?**
Below is the complete workflow:
Step 1: Install Hermes
Core question: How do you set up the agent runtime environment?
Installation:
curl -fsSL <install_script> | bash
Setup process:
-
Launch installer
-
Choose Quick Setup
-
Configure your model:
-
Local: Ollama + Gemma 4 (zero API cost) -
Cloud: Claude or GPT-Codex (stronger reasoning)
-
Verification:
hermes doctor
hermes chat -q "Hello, what tools do you have?"
Key details:
-
Supports 200+ models -
Works locally, on VPS, or Docker -
Includes persistent cross-session memory
Step 2: Install Moss Trade Bot Factory Skill
Core question: How do you enable trading capabilities in Hermes?
This step is essential.
Once installed, Hermes can:
-
Interpret trading strategies from natural language
-
Generate 30+ quantitative parameters, including:
-
Leverage -
Long/short bias -
Entry thresholds -
Stop-loss multipliers -
Signal weights
-
This is the transformation layer:
Natural language → executable trading strategy
Step 3: Describe Your Strategy in Natural Language
Core question: How do you define a trading agent without writing code?
Example:
I expect BTC to enter a ranging market.
I need a trading agent that uses short-term signals
to trade both long and short directions,
with a target return above 100%.
Hermes will:
-
Call the Skill -
Generate parameters -
Run backtests -
Output results
Key shift:
You are no longer coding strategies—you are defining intent.
Step 4: Iteration and Strategy Evolution
Core question: How does Hermes optimize strategies—and why does it outperform?**
This is where the real advantage emerges.
In the experiment:
-
70 random parameter explorations (escape local optima) -
Selection of seed configurations -
Secondary optimization over 22 evolution schedules
This means:
Hermes doesn’t just tune parameters—it optimizes how tuning itself is done.
Performance comparison:
| Method | Backtest Return |
|---|---|
| Hermes (random + meta search) | +157% |
| Linear tuning | +21% |
Conclusion:
Performance differences come from search strategy, not model choice.
Step 5: Deploy to Moss Live Mode
Core question: How do you move from backtesting to real trading?**
Process:
-
Export final parameter file -
Upload to Moss live mode -
Start agent execution
Execution characteristics:
-
Uses real market data -
All trades are recorded -
Performance is publicly visible via leaderboard
3. What Extra Value Does Hermes + Moss Provide?
Core question: Why not just use Moss directly?**
1. Deep Strategy Search
Answer: Hermes enables multi-round autonomous optimization.
| Mode | Behavior |
|---|---|
| Moss Hosted Agent | Single-pass generation |
| Hermes | Multi-iteration optimization |
Capabilities include:
-
Randomized exploration -
Segment-based backtesting -
Failure analysis -
Evolution strategy tuning
2. Cross-Session Memory
Answer: The agent retains long-term context.
Examples:
-
“Avoid trading before major events” → remembered weeks later -
Strategy comparisons across months → retrievable instantly
3. Skill-Based Automation
Answer: Repetitive workflows become reusable automation.
Example command:
Run weekly strategy review
Automatically executes:
-
Backtesting -
Metrics evaluation -
Parameter adjustment -
Comparative reporting
4. Model Flexibility
Answer: You can assign different models to different tasks.
Example setup:
| Task | Model |
|---|---|
| Strategy generation | Claude |
| Queries | GLM 5.1 |
| Validation | Gemma 4 |
Important:
-
Execution is deterministic (handled by Moss) -
Models only influence parameter generation
4. Key Insights from the Experiment
Core question: What general lessons can be extracted?**
1. Search Strategy Determines Outcome
Not how long you search—but how you search.
2. Parameter Packaging Affects Real Performance
Hermes design:
-
No hardcoded timeframe -
No fixed symbol -
Strategy logic only
Benefits:
-
Reusable across environments -
More flexible deployment
3. Backtesting Validates the Agent, Not Profit
Test scenario:
-
BTC drop from 123K to 68K
Focus:
-
Can the agent complete the full pipeline? -
Can it iterate and deliver stable outputs?
4. Data Integrity Is Critical
Hermes ensures:
-
Consistent data across iterations -
Verifiable outputs
Implication:
Incorrect data leads to cascading failures in trading decisions.
5. Dual “Soul” Architecture: SOUL.md vs Strategy Description
Core question: How is agent behavior structured?**
Two layers:
1. Hermes Layer (SOUL.md)
Defines:
-
Communication style -
Reasoning approach -
Uncertainty handling
2. Moss Layer (Strategy Description)
Defines:
-
Market bias -
Leverage -
Entry/exit rules
Parameter categories:
| Type | Description |
|---|---|
| Personality parameters | Fixed |
| Tactical parameters | Evolves ±30% weekly |
Key takeaway:
The two layers are completely independent.
6. Who Should Use Hermes + Moss?
Core question: Is this setup right for you?**
Ideal users:
-
Existing Hermes users -
Traders seeking deep optimization -
Users needing specific models -
Those requiring full data control -
Developers building automated pipelines
Not ideal for:
-
Users wanting instant setup -
Those not interested in optimization depth
Alternative: Moss Hosted Agent
7. Emerging Architecture: General Framework + Vertical Engine
Core question: What trend does this represent?**
The ecosystem is splitting into layers:
| Layer | Function |
|---|---|
| General frameworks (Hermes) | Run agents |
| Vertical systems (Moss) | Execute domain-specific logic |
Relationship:
Complementary, not competitive
8. Practical Reflections
Core question: What actually changes in practice?**
1. Search > Parameters
The real leverage is in exploration strategy.
2. Process > Outcome
What matters:
-
Reproducibility -
Iterability -
Transparency
3. Structure Enables Scale
Design choices like:
-
Parameter/environment separation -
Dual-layer architecture
enable long-term extensibility.
9. Practical Checklist
Core question: How do you implement this quickly?**
-
Install Hermes -
Configure model -
Install Moss Trade Bot Factory Skill -
Describe strategy -
Let Hermes iterate -
Export parameters -
Deploy to Moss live mode
10. One-Page Summary
-
Hermes = agent operating system -
Moss = trading execution engine -
Skill = connection layer
Workflow:
Describe → Generate → Optimize → Execute
Key advantages:
-
Autonomous strategy search -
Persistent memory -
Workflow automation -
Model flexibility
Core insight:
Strategy quality is determined by search methodology, not the model itself.
11. FAQ
1. Does Hermes execute trades?
No. Execution is handled entirely by Moss.
2. Does model choice affect trading results?
Only indirectly via parameter generation.
3. Can I use local models?
Yes, local models are supported.
4. Are Hermes and Moss tightly coupled?
No. They are connected via a Skill layer.
5. Do backtest results guarantee live performance?
No. Live trading is the final validation.
6. Can workflows be automated?
Yes, through reusable Skills.
7. Are parameter files reusable?
Yes, they are designed for cross-environment reuse.
8. Is this beginner-friendly?
Not ideal. Beginners should consider hosted solutions first.
