The bait, then the rug-pull.
The title promises 100 hours compressed into 46 minutes, and the cold open delivers immediately: a Figma-style whiteboard shows seven numbered levels with escalating icons, and the host walks each one before the first minute is up. No fluff, no preamble.
Where the time goes.
01 · Level 1 — VPS install
SSH into Hostinger VPS, one-liner Hermes install, OpenRouter API key, first successful chat. Sponsor segment.
02 · Level 2 — Discord gateway
Create Discord bot app, enable three privileged gateway intents, generate bot invite URL, install Hermes gateway as systemd service, confirm bot is online.
03 · Level 3 — Curator
hermes update, check curator status, 30-day stale / 90-day delete thresholds that prevent skill bloat.
04 · Level 4 — Cron backup to GitHub
Create private GitHub repo, fine-grained PAT scoped to contents, store via hermes config set, daily 3 AM backup cron job, verify first push.
05 · Level 5 — Kanban multi-agent
Hermes v0.12.0 Kanban; prompt Hermes to self-configure; SSH tunnel to localhost:9119; four specialist profiles; four-task parallel content research pipeline.
06 · Level 6 — Holographic memory
Five reasons default memory fails; hermes memory setup to local SQLite holographic store; seed from previous sessions; use cases: sponsor history, VPS health, contradiction detection.
07 · Level 7 — Hermes as MCP server
Install Claude Code on VPS, claude mcp add hermes, verify 10 MCP tools available. Three use cases: remote approval gate, walk-away mode, phone triage. Demo succeeds.
Visual structure at a glance.
Named ideas worth stealing.
Seven Levels of Hermes Agent
- VPS install
- Discord gateway
- Curator
- Cron automations
- Kanban multi-agent
- Holographic memory
- MCP server
Progressive depth model — each level is additive and depends on the previous.
Five reasons holographic memory beats default RAG
- Beginners never save anything
- Bigger context is not memory
- RAG searches by vibes not structure
- Embeddings cost money and leak data
- Summaries blur over time
Five-point argument for why default memory patterns fail and local structured fact stores win.
Three MCP server use cases
- Remote approval gate
- Walk-away mode
- Phone triage
Three canonical reasons to expose Hermes as an MCP server to other agents.
Lines you could clip.
"If you watch until the end, you're gonna have a more powerful Hermes agent setup than 99.9% of people."
"Don't be cheap. Don't use a small model. Use the most powerful model available."
"I think the ultimate paradigm is each agent runs on its own computer so it can set it up in a way that it needs to be most effective."
"Claude Code couldn't do this. It doesn't have access to your Telegram or Discord."
Things they pointed at.
How they asked for the click.
"Make sure to join the new society. The link to the new society landing page will be below the video."
Two placements: mid-video after Level 1, and end-of-video. Tied to a time-limited offer (GitHub repo audit for May joiners) plus a new Hermes mastery course.
Word for word.
Seven decisions that define how powerful your AI agent actually is.
The gap between a basic Hermes setup and a seven-level one is not technical complexity — it is seven deliberate configuration choices that each multiply what the agent can do independently.
- An agent that lives on a VPS instead of your laptop runs 24/7, holds its own API keys securely, and is not blocked by your machine being asleep or closed.
- Connecting a messaging platform turns an agent from a terminal tool into something you can interact with from your phone without opening a laptop.
- Curator exists because self-improving agents generate skills continuously — without a stale-skill pruning threshold, token costs and context bloat compound silently over months.
- Storing agent tokens via a config command keeps secrets out of conversation context, preventing the AI from accidentally leaking them in tool outputs or logs.
- A Kanban board with specialist profiles lets four sub-agents work in parallel on dependent tasks without you managing the handoffs manually.
- Default memory dies at session end; holographic memory persists structured facts locally in SQLite, meaning the agent remembers your sponsor history, VPS config, and preferences across every future session.
- Exposing an agent as an MCP server is the only way to give Claude Code access to your Telegram and Discord history, approval flows, and messaging infrastructure.
- The practical value of a remote approval gate is the difference between an agent that stops and asks before doing something destructive and one that executes destructive operations unattended at 3 AM.
- Cheap models fail in complex agentic harnesses before they fail in simple chat; debugging costs almost always exceed the token savings from downgrading the model.






























































