Skip to content

Profile Isolation

Profile Isolation is a design principle that ensures complete separation of state, configuration, and execution environments between different operational contexts^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md].

In systems that implement this principle, such as the Hermes Agent, each profile operates as an independent instance with its own dedicated runtime resources. This is achieved by assigning a unique HERMES_HOME directory to each profile, which serves as the root for isolated storage of configuration files, memory databases, session histories, and process IDs^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md].

Core Mechanisms

True isolation requires strict separation across several layers of the system:

  • Environment Separation: Each profile maps to a distinct home directory (HERMES_HOME).
  • Data Isolation: Configuration (config), long-term memory (memory), and conversational history (sessions) are stored separately and never shared between profiles^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md].
  • Process Isolation: Background processes, such as Gateway daemons, are tracked and managed via unique Process IDs (PIDs) specific to that profile^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md].

This architecture allows multiple profiles to run simultaneously on the same deployment without conflict^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md].

Usage Scenarios

Profile Isolation is critical in scenarios where distinct contexts or user personas must be maintained on the same infrastructure^[001-TODO__Hermes_Agent_·_设计哲学与思维框架.md]:

  • Multi-User Environments: Different users sharing a single server or deployment can maintain separate private environments.
  • Multi-Context Workflows: A single user may operate distinct profiles for separate projects, clients, or roles (e.g., "Work" vs. "Personal") to prevent cross-contamination of memory and settings.

Sources

  • 001-TODO__Hermes_Agent_·_设计哲学与思维框架.md