Nous Research's Hermes Agent Now Lets You Pack and Share Entire AI Setups
Hermes Agent profiles are now a single portable file, letting you share full agent setups with credentials safely stripped out
- Hermes Agent now supports
/exportand/importslash commands to pack and restore full agent profiles as a single file. - Exported profiles include skills, memory, persona (SOUL.md), cron jobs, plugins, and desktop themes -- credentials are always stripped.
- The feature solves the longstanding problem of sharing a fully configured agent setup without manual file copying or leaking secrets.
- A separate "Profile Distributions" system (git-based) exists for versioned, team-scale agent sharing with one-command installs and updates.
- Hermes Agent is fully open-source (MIT), free to use, and runs on Linux, macOS, and WSL2.
- The feature is available now; see the official docs for the full CLI reference.
Hermes Agent, the open-source self-improving AI agent from Nous Research, just made one of its most-requested quality-of-life improvements: profiles are now fully portable. Two new slash commands, /export and /import, let you pack an entire agent setup into a single file and load it anywhere, no manual file-copying required.
What a profile actually contains
If you haven't used Hermes before, a quick orientation: Hermes is the only open-source agent with a true built-in learning loop -- it doesn't just complete tasks, it remembers, builds reusable skills, and gets smarter every time you use it. All of that accumulated state lives inside a profile.
A profile is more than a config file. A profile has its own config, .env, memory, skills, sessions, and gateway setup under ~/.hermes/profiles/<name>/. People build highly specialized ones: a custom SOUL.md (the agent's personality), curated skills, MCP server connections, pipeline settings, cron jobs -- the works.
The problem this solves
Imagine someone builds a "Code Review Specialist" profile, or a "Research Assistant" profile, complete with the right SOUL, the right skills, the right MCP connections, and the right cron schedule. Until now, there was no way to share that as a unit. You could push individual skill files to GitHub, but the creation context, design decisions, and configuration that made those skills actually useful were lost the moment the session ended.