Before You Create a Hermes Bot, Lock Down These 3 Things

Hermes bot mode isn't a new kind of worker — it's a desktop roster for profiles you already have. Naming a bot, giving it a face, and dropping it in a list doesn't separate what it can reach. A new bot shares the main profile's OAuth and token pool by default, and Nous states plainly that a profile is not a file system sandbox. The roster is where you see the owner. The profile is where the access question actually lives. I checked Nous's bot mode and profiles guides against the shipped desktop source and 254 passing plugin tests, and I'm labeling every claim by the receipt that earned it — including the part where I stopped the test early. In this video I break down: What a bot actually is in Hermes (a profile with a name, a face, and a chat surface) Why three names on a roster does not mean three safe workers What a profile really carries: env file, soul, memories, sessions, skills, cron jobs, state The shipped creation controls — General, Advanced, Capabilities — and which ones your role actually needs What the name does NOT separate: shared OAuth, shared token pool, and host-level reach Cron jobs vs scheduled jobs — two different services people keep confusing Trigger now, run history, and why results land in that bot's own chat Group rooms: the real limits of 2-6 bots, 3 serial rounds, 10 messages per send Why live interruption of a running bot is still future work Bot-to-bot messaging and cross-machine paths — and the conditions they actually require The production correction: why I stopped the isolated test when Hermes reached a credential store Evidence tiers — how to label a claim by the receipt that earned it, not the one you wish you had The one founder decision that should never come back through a bot If you're a founder or operator putting named agents near real work, this is the boundary check before you hand any of them access. TIMESTAMPS: 0:00 – Three Names Doesn't Mean Three Safe Workers 0:25 – What You'll Get From This Video 0:47 – Meet Johnny Nel 1:22 – What a Bot Actually Is (A Profile With a Face) 1:49 – The Role Cards: Maya, Theo & Nia 2:02 – Roster vs Profile: Where the Real Question Lives 2:24 – What a Profile Actually Carries 2:50 – The Creation Controls: General, Advanced & Capabilities 3:13 – Does This Role Even Need That Setting? 3:46 – What the Name Does NOT Separate 3:56 – "A Profile Is Not a File System Sandbox" 4:10 – Why a Roster Is Not an Access Boundary 4:37 – The Boundary Starter Kit 5:04 – Cron Jobs vs Scheduled Jobs (Not the Same Thing) 5:29 – Trigger Now & Run History 5:51 – Should You Schedule a Bot Straight Away? 6:20 – Group Rooms: 2-6 Bots, 3 Rounds, 10 Messages 6:46 – Do Your Roles Actually Change the Answer? 7:04 – What We Did NOT Run (And Why That Matters) 7:26 – Bot-to-Bot Messaging & Cross-Machine Paths 7:49 – The Production Correction: The Credential Store 8:14 – Evidence Tiers: What the Screen Earned 8:49 – Big Takeaways 9:26 – Start With One Narrow Role 🔓 Want the actual system — the folder structure, the wiring, the templates, ready to copy into your own setup? It's inside the AI Founders Vault: 👉 https://www.skool.com/aifoundersvault Join The AI Founder's Vault Skool Community here: https://www.skool.com/aifoundersvault Lets connect:   / johnnynel_     / johnnynelofficial     / johnnynelofficial   -    / @johnnynelofficial