The argument in one line.
Connecting Hermes AI agent to Claude Code through shared memory, Pantheon personas, and API integrations like Apollo and Gmail creates a unified intelligence system that maintains full context across both coding and conversational work.
Read if. Skip if.
- You're a solo founder or operator running a technical AI stack locally and want to connect Hermes, Claude Code, and business tools into one unified memory system.
- A developer or technical founder who uses Telegram for brain dumps and Claude Code for building, and wants context from one system to automatically inform the other.
- You're already using Hermes or Claude Code individually and want to layer on lead scraping, email automation, and persistent memory without rebuilding your workflow.
- You're not comfortable with local AI setup, GitHub, or connecting APIs — this requires hands-on technical execution, not just conceptual understanding.
- You need a no-code solution or are looking for AI agent setup that doesn't involve running Hermes locally or wiring custom integrations to your own systems.
The full version, fast.
This walkthrough shows how to wire an open-source AI agent on Telegram into the same shared memory that Claude Code already builds on your machine, so neither side loses context when you switch from coding at the desk to dictating from your phone. The method is a three-step install: connect the agent via a single terminal command using your existing model credentials, mirror its config and persona files to a private GitHub repo so they survive machine swaps and can be rolled back, then bridge it to your Obsidian vault and Claude OS dashboard for cross-tool recall. From there you layer skills like Apollo prospecting and Zapier-to-Gmail, scoping each integration to draft-only and read-only permissions so the agent can act without going rogue.
Chat with this breakdown.
Modern Creator members can chat with any breakdown — ask for the hook, quote a framework, find the exact transcript moment. Unlocks at T2: refer 3 friends + add your own API key.
Create a free account →Where the time goes.

01 · Hook + problem frame
10X claim plus credibility. Introduces the Two AIs Zero handshake pain point.

02 · Visual intelligence layer
Claude Code OS dashboard tour: AI spend across models, overnight dreams feature, independent memory systems, Pantheon preview.

03 · Installing Hermes from scratch
Terminal install command, Telegram bot creation, bot token and allowed user IDs, first confirmed response.

04 · Building and backing up the Pantheon
Named personas (Labyrinth/Mercury/Philosopher), GitHub mirror for config persistence, cron backup at 11PM, folder-based auto-discovery architecture.

05 · Obsidian agentic memory
Vault path lookup via Claude Code, memory confirmation in Hermes, real-time memory save demo.

06 · Claude OS bridge + morning cron
Feeding Hermes access to Claude chat logs, 8AM morning brief cron with GPT 5.5, automated overnight reflection.

07 · Apollo lead scraping skill
Why Apollo (B2B database, intent signals, sequences built-in), API key setup, live demo: 20 Austin roofing companies with pain-point brief and prioritized outreach list.

08 · Zapier MCP — Gmail + Calendar
Principle of least access applied to tool selection (draft only, no send), 7 Gmail tools plus calendar, live calendar query demo. CTA to next video.
Lines worth screenshotting.
- The biggest problem with any AI assistant is that what you do in Claude Code never reaches your mobile agent, and what you tell your Telegram bot never reaches your coding session.
- Bridging a local AI coding environment and a mobile AI assistant through a shared memory folder solves the context fragmentation problem that every multi-tool AI user hits.
- Named personas with specific models and system prompts — a research persona using DeepSeek, a background automation persona using a cheap model — let you right-size compute to the actual task.
- Never give an AI agent the ability to send emails, only draft them — the principle of least access applied to email is non-negotiable until you trust the model's judgment completely.
- Backing up your Hermes configuration to a private GitHub repo means your personas and settings survive machine swaps and can be rolled back if something breaks.
- Apollo's B2B database costs money for a reason: scraped data typically hits only a fraction of the contacts, while reliable paid databases dramatically improve email delivery rates.
- Zapier's MCP integration turns any popular SaaS into an AI-connectable tool in under five minutes — the Willy Wonka of automation connectors.
- A cron job that queries all your AI chat logs overnight and generates 2-3 improvement suggestions each morning is a free coaching layer running on cheap models.
- The soul.md file is where you brain-dump everything about yourself so your agent knows your context, preferences, and goals without requiring repetition.
- Connecting Obsidian to a Telegram AI agent gives that agent access to your personal knowledge base during any mobile conversation, anywhere.
The handshake is the product.
The next content category is not how to use AI — it's how to make your AIs talk to each other.
- Jack's Two AIs. Zero handshake. slide is the whole pitch in four words. Build that sentence for whatever fragmentation your audience feels.
- The Pantheon folder-based architecture (each persona = one YAML file) is a dead-simple extensibility pattern — steal it for any multi-model routing system.
- Morning brief cron is a product feature, not a tutorial trick. An AI that thinks overnight and brings you 2-3 ideas at 8AM is a different category than a chatbot.
- The principle of least access is a trust-builder. One sentence in a permissions flow is the difference between this feels sketchy and this person knows what they are doing.
- Jack's custom marketing page inside the tutorial — the mythology artwork, the bold headlines — elevates a screen-share tutorial into a product reveal moment. Worth replicating in your own demos.
Terms worth knowing.
- Hermes
- An open-source AI agent assistant that runs on Telegram and is designed to think, dream, and self-improve based on ongoing conversations and memory.
- Claude Code
- Anthropic's command-line coding tool that lets developers work with the Claude model directly inside their terminal to write, edit, and ship code.
- AI operating system
- A dashboard layer that unifies models, chat logs, memory, and integrations from multiple AI tools so a single agent can read and act on everything in one place.
- Handshake (between AI systems)
- A shared connection that lets two AI tools exchange context and memory, so work done in one is visible and usable to the other.
- Pantheon
- A collection of named sub-agent personas inside Hermes, each with its own system prompt, role, and assigned model for handling specific kinds of tasks.
- Persona (AI)
- A named character given a description, system prompt, and model so it behaves consistently for a defined job like research, planning, or tool calling.
- System prompt
- The hidden instruction that defines an AI's role, tone, and rules before any user message, shaping how it responds throughout the session.
- Labyrinth
- A Pantheon persona built for deep research and wrestling with ambiguous problems, typically assigned a heavier reasoning model.
- Mercury
- A Pantheon persona used for autopilot and scheduled background work, usually paired with a cheap or fast model to handle routine tasks.
- Philosopher (persona)
- A Pantheon persona prompted to surface the question behind the question and reason from first principles rather than answer directly.
- Oracle (persona)
- A Pantheon persona configured for predictive or interpretive responses, defined by name, description, prompt, and chosen model.
- Codex (OpenAI)
- OpenAI's coding agent CLI included with a ChatGPT subscription, used here as one of the model backends Hermes can route requests through.
- Antigravity
- An AI-assisted coding environment with a built-in terminal, used in the walkthrough to run installation scripts and talk to the Hermes setup.
- DeepSeek
- A low-cost open-weights language model often assigned to background or research personas where heavy reasoning is wanted but budget matters.
- Telegram bot
- An automated chat account on Telegram, created through the BotFather account, that exposes an API token so external software can send and receive messages.
- BotFather
- Telegram's official bot for creating and managing other bots; you message it to register a new bot and receive an authentication token.
- Bot token
- A secret string issued by BotFather that authenticates an application's requests to the Telegram API on behalf of a specific bot.
- Allowed user IDs
- A whitelist of Telegram account IDs permitted to message a private bot, so only the owner can talk to it and trigger actions.
- VPS
- A virtual private server — a rented always-on machine in the cloud used to host services that need to stay online when a personal computer is off.
- Compression threshold
- A setting that controls how full an agent's context window must get before the system summarizes older messages; higher values compress less often but cost more memory.
Things they pointed at.
Lines you could clip.
“There's a Hermes on the walk, you open Claude code, you type it again, it's never seen again.”
“We don't need Albert Einstein to wash off to mop our floors. We want Albert Einstein scribbling on a whiteboard in a very esoteric area.”
“The delta between idea and average should be small.”
“The principle of least access — any tool connection has the fewest possible tools available to actually do the thing.”
Word for word.
The bait, then the rug-pull.
Jack Roberts opens with a promise that sounds inflated until he shows the marketing slide: two AIs, zero handshake. Claude Code knows your repos and 2AM bug fixes. Hermes knows your Telegram brain-dumps. Neither has ever met the other — and every context switch forces you to re-explain your entire world from scratch.
Named ideas worth stealing.
Two AIs. Zero handshake.
Visual problem frame — any two AI tools you use independently share no memory. The handshake is the product.
Pantheon architecture
- Each persona = one YAML file
- Drop file in folder = new agent
- Hermes auto-discovers
- Model + role + system prompt per persona
Extensible sub-agent routing via filesystem. Add new capability = add a file. No code changes.
Principle of least access
Only grant a tool connection the minimum permissions needed to do its job. Applied to Zapier MCP tool selection (draft yes, send no).
Morning brief cron
Cheap model runs overnight, reads all chat logs, delivers 2-3 actionable suggestions at 8AM. Passive intelligence without active prompting.
How they asked for the click.
“The next thing we're gonna do is learn how to build this agentic system for Claude, which we're gonna do in this video right here.”
Low pressure end-card CTA. No subscribe ask, no newsletter pitch. Clean tunnel to next video in the series.








































































