When Hermes profiles may not be enough separation
Hermes is being used through Matrix mobile clients with Deepseek, and the main issue is how to split purpose-built agents. Separate work areas are wanted for coding, research, , and other task types, so each one can keep its own context and focus. An should ideally be able to work across profiles.
Matrix channels should also be limited so only certain profiles listen and reply, such as a security channel handled by a security-focused profile. Family members may get access to the same Hermes Matrix server, but private personal context must not leak into shared family use. Family access also must not accidentally create a path into the main agent, especially if that agent can reach sensitive , keys, account details, or higher .
The unclear choice is whether a separate profile is enough or whether a separate Hermes instance is needed. also matters on a VPS with 2 virtual CPUs, 4 GB of RAM, and 11 GB of free storage.
Key points
- Hermes is being used with Matrix mobile clients and Deepseek.
- The desired setup separates coding, research, , and other work into focused agents.
- Some Matrix channels should only be handled by specific profiles, such as a security profile.
- Shared family access must not leak private personal context or reach sensitive .
- The open question is profile separation versus a separate Hermes instance on a small VPS.