Thread Truncated (Cap Enforced)
Only the first 20 tweets are unrolled into slides to ensure reliable PDF exporting and high server performance.
Canvas & Ratio
Choose your destination platform format
Layout Template
Choose a content structure for your slides
Preset Themes
Typography & Sizing
Brand Kit Customization
AGENCYConfigure brand assets for headers & footers
Outro Slide CTA
Customize your closing call-to-action slide
Background Pattern
Build Your Carousel
Drag and drop any post card below onto a slide, or use the quick buttons to insert content/images instantly!
I ran one hermes agent as researcher, writer, coder, and orchestrator for 14 days on a single claude-sonnet-4.6 profile before everything blurred into the same voice. Most operators blame the prompt when this happens, but it is not prompting and not the model - it is one agent carrying five roles on shared memory, and everyone says "better prompts" while nobody talks about the Hermes primitive that actually fixes it: isolated profiles.
@neoaiforecast posted the team build last week: orchestrator + alan + mira + turing, four roles, clean handoffs, 1,317 bookmarks in a day. The build is correct, but it stops at day one. This guide picks up at day two and takes you through the operator layer that keeps a 4-profile team coherent on day 30 -handoff contracts, memory-kpi per profile, policy gates per role, and the four failure modes nobody posts screenshots of.
If you ignore the operator layer, your team collapses into a single blurry agent within a month.
Below: the mental model, the 4-role team, the 7-step build, the operator runbook, the day-30 failures, and a copy-paste team-agents.md template.
Save this to your bookmarks.
## The mental model — roles, not personas
The wrong mental model is: I need one genius AI that does everything.
The better mental model is: I need a small team with distinct roles, clear handoffs, and less context pollution.
Hermes profiles are the primitive that makes this real. They are not character skins. Each profile isolates seven pieces of state at once:
• configuration
• sessions
• memory
• skills
• personality
• cron state
• gateway state
That matters because multi-agent setups fail when everything shares the same memory and tone. Your coding agent should not inherit the defaults of your research agent. The research agent should not carry the writer's stylistic habits. Specialization becomes durable only when the state remains separated.
## The 4-role team
Credit to @neoaiforecast for naming the canonical split. Four profiles, mapped to real functional work:
• <b>Hermes</b> — orchestrator. plans, decomposes, routes, synthesizes. the traffic controller, not the bottleneck.