🐕 Hermes = your Labrador
The central analogy: Hermes is like your dog. It lives with you, gets to know you and improves year after year. It's not a tool you turn on and off: it's a long-term relationship.
🏡 What “living with you” means
- •Persistence: remembers who you are between conversations
- •Familiarity: learns your style, routines, and projects
- •Evolution: it gets more useful each month, not less
💡 Practical tip
Treat Hermes as a long-term companion: invest in it early (memory, soul, integrations), and the returns grow over time.
👷 Claude Code = the contractor
O Claude Code is the contractor: excellent for a specific job, a precision tool. But it doesn’t live with you doesn’t even remind you next time.
✓ The contractor is great for
- ✓Precision technical work (code)
- ✓One-off tasks with a beginning, middle, and end
- ✓Depth in a specific project
✗ What the contractor does NOT do
- ✗Remember you in the next session
- ✗Keep you company day to day
- ✗Build a long-term relationship
Important: it’s not “better or worse” — they have different roles. Module 3.7 shows how to connect the two so they share memory.
🛋️ OpenClaw & anti-gravity
To complete the map: the OpenClaw is the roommate and the anti-gravity is your IDE/coding partner. Each piece of the ecosystem serves a purpose.
Hermes — your dog
Lives with you, knows you, and gets better over time. A persistent companion.
Claude Code — the contractor
Precision tool for one job; it won't remind you later.
OpenClaw — roommate
Shares the workspace with you in your workflow.
anti-gravity — your IDE/partner
The environment where you program side by side with AI.
📈 The More You Use It, the Better It Knows You
The essence of Hermes: the more you use it, the more it gets to know you — and the more useful it gets. The value compounds: it grows over time rather than appearing all at once on day one.
📊 Accumulation effect
- •Day 1 — a generic agent, capable but unfamiliar with you
- •Weeks later — knows your projects, contacts, and preferences
- •Months later — anticipates what you need before you ask
💡 Practical tip
Don’t judge Hermes by your first use. The real benefit appears once it has built up context about you — memory (Track 2) is what powers that.
🏃 When to use Hermes (and when not to)
Simple rule: use Hermes when you are mobile — coffee shop, gym, on your phone. Use desktop tools when you’re on the desktop, with focus and keyboard.
✓ Prefer Hermes
- ✓Away from your desk (coffee shop, gym, outdoors)
- ✓On your phone while you're on the go
- ✓Tasks that depend on your personal context
✗ Prefer desktop tools
- ✗Long coding session at the desk
- ✗When you need an IDE and keyboard
- ✗Precision work on a technical project
🎨 Design ethos: living with you
Hermes’s design principle is live with you and improve over time — not to be a disposable tool. This ethos explains practically every other product decision.
🧬 The ethos in concrete decisions
- •Local memory (Track 2) — to build up context about you
- •Soul.md — to give it your personality and your way of doing things
- •GitHub backup (Track 3) — so you never lose the relationship you've built
💡 Practical tip
Whenever a decision Hermes makes seems strange, ask: "does this help him live with me and improve?" — the answer usually explains why.
🧯 Common mistakes & the pocket guide
Before you wrap up: the most common pitfalls for beginners — and a quick reference for which tool to use in each situation.
✓ Do it
- ✓Give it time: value grows with use
- ✓Invest early in memory and soul
- ✓Choose the tool based on the context (mobile vs. desktop)
✗ Avoid
- ✗Expecting "magic" on day one
- ✗Expecting Claude Code to remind you later
- ✗Use Hermes for tasks that call for an IDE and keyboard
Pocket guide (which tool to use)
móvel / acompanha você / contexto pessoal -> 🐕 Hermes job técnico de precisão / sessão única -> 👷 Claude Code colega no fluxo de trabalho -> 🛋️ OpenClaw ambiente de código lado a lado -> 🧑💻 anti-gravity (IDE)
📌 Module Summary
Next Module:
1.3 — One Brain, 22 Mouths