video1.0<iframe src="https://www.loom.com/embed/70da16b66039490dbb9191d95e7126fe" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/70da16b66039490dbb9191d95e7126fe-7840aa99592ccaf9.gif1296.536This Loom explains how the speaker redesigned their Hermes setup, emphasizing a profile based system and a strict file structure instead of generic tutorials. They break down Hermes folders like solmd for agent identity and enforcing file discipline, plus memories, sessions, skills, crons, logs, and other supporting components. The core decision is using separate profiles as separate agent instances with their own solmd, memory, skills, and models, while keeping a separate workspace folder that only stores context and never code. They describe selling these Hermes profiles as AI employees to residential contractors via a context operating system on a virtual server, including examples like schedule and material procurement employees, and note an upcoming YouTube video release on the Material Runner this week.