Requirements and responsibilities
Assign a named team owner for this task and confirm that all needed service accounts, sources and data are within the approved scope. Never place credentials or private keys in agent prompts.
Use the installed Hermes version and upstream feature documentation for this procedure; it does not establish that xCloud enables the feature by default.
Illustrative situation
Illustrative scenario: a team owner wants a durable writing preference carried across fresh sessions and needs proof the instruction was written to memory.
Choose the approach
Store only stable, non-secret team preferences in durable memory; keep task-specific or sensitive information in its approved source system.
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Choose durable, safe conventions
- Where
- Team owner / approved memory request
- Permissions
- Team knowledge owner
- Inputs
- Short preferences useful across tasks; no secrets or sensitive personal data
- Action
- Select a few stable writing or reporting preferences. Keep task-specific or confidential facts out of durable memory.
- Expected result
- The proposed memory has a named owner and limited content.
- Verify
- Review the exact text before asking Hermes to save it.
- If it fails
- If a convention is uncertain or sensitive, omit it and keep it in an approved system of record.
Sources: Hermes memory feature guide
Step 2 of 5
Locate the active profile and save the approved entry
- Where
- Hermes terminal/CLI and active Hermes profile
- Permissions
- Authorized Hermes user
- Inputs
- Active HERMES_HOME/profile; approved exact preference; target memory type
- Action
- Run `hermes profile list` and identify the active profile/HERMES_HOME before writing. Use the profile’s `memories/MEMORY.md` for environment or team conventions and `memories/USER.md` only for personal preferences; the default profile uses `~/.hermes/memories/`, while named profiles use `~/.hermes/profiles/<profile>/memories/`. Ask Hermes to use the memory tool to save the exact approved text to the correct target.
- Expected result
- The preference is assigned to the right profile and memory target.
- Verify
- Do not treat an acknowledgment as persistence; inspect the target MEMORY.md or USER.md content.
- If it fails
- If the file was not changed, retry using the actual supported memory operation, not narrative prompting.
Sources: Hermes memory feature guide
Step 3 of 5
Inspect the active profile memory file
- Where
- Authorized Hermes terminal/CLI using the active profile path identified above
- Permissions
- Workspace owner
- Inputs
- The active profile path, MEMORY.md or USER.md target, expected text
- Action
- Open the file under the active profile’s `memories/` directory, not a different default profile. Confirm the exact entry is present; `MEMORY.md` holds environment/conventions and `USER.md` holds personal preferences.
- Expected result
- The approved entry appears in the correct active-profile file and target.
- Verify
- Compare saved text with the approved wording and inspect the tool result for a successful write; an acknowledgment alone is not proof.
- If it fails
- If wrong or overbroad, edit/remove the entry and verify the corrected file.
Sources: Hermes memory feature guide
Step 4 of 5
Verify fresh-session loading
- Where
- Hermes conversation
- Permissions
- Authorized user
- Inputs
- A new Hermes session boundary, e.g. /new
- Action
- Start a new Hermes session using that same profile (for example `/new` on a gateway or a fresh CLI invocation). Ask a harmless task that should use the preference and check the fresh session’s behavior.
- Expected result
- The new session uses the saved convention or transparently says it cannot find it.
- Verify
- Confirm the profile matches and the new session applies the saved preference; if not, inspect the profile-specific file and memory-enabled settings.
- If it fails
- If it does not load, inspect memory file location/snapshot behavior in official docs; do not claim the preference persisted.
Sources: Hermes memory feature guide
Step 5 of 5
Maintain the memory responsibly
- Where
- Team memory owner
- Permissions
- Memory file write permission
- Inputs
- Review date and removal owner
- Action
- Review memory periodically, remove stale items, and keep durable memory bounded and non-secret.
- Expected result
- The memory remains useful and owned.
- Verify
- Confirm removals are reflected in the file and test if relevant.
- If it fails
- If ownership changes, remove team-specific instructions until a new owner approves them.
Sources: Hermes memory feature guide
Maintenance
Have the memory owner review MEMORY.md/USER.md for stale or sensitive entries; verify every edit in the file and test important changes in a fresh session.
Recovery decisions
If the new session does not apply a convention, inspect the actual memory file and session boundary; correct or remove the entry. Do not treat a gateway reboot as a fresh session.
AI handoff
Configure the needed provider, channel, credentials and permissions separately. This guide does not imply xCloud has preconfigured upstream tools or scheduled jobs.
Supported scope
- Review the task result and retain human control app · manual
Human acceptance and follow-up; no external write is implied.
Checkpoint: Verify the source/output and actual side effects before sharing or acting.
Hermes security guide · Hermes daily briefing tutorial · Hermes automate with cron patterns
- Use the authorized Hermes terminal, CLI or documented task interface app · manual
Upstream Hermes CLI/configuration workflow; requires an authorized operator and does not prove xCloud preconfigured the feature or exposed it in its panel.
Checkpoint: Check the installed Hermes version and current upstream instructions; review scope and permissions before running a task.
Hermes quickstart · Hermes cron feature guide · Hermes memory feature guide · Hermes skills feature guide · Hermes agent email address tutorial · Hermes GitHub PR review agent tutorial · Hermes delegation feature guide
Copyable agent brief
Manual checkpoints
- Use `hermes profile list` to identify the active profile, then inspect that profile’s `memories/MEMORY.md` or `memories/USER.md`. Default path is `~/.hermes/memories/`; a named profile has `~/.hermes/profiles/<profile>/memories/`. Use `/new` or a fresh CLI invocation to reload the frozen snapshot.
- Review the task-specific acceptance check and inspect actual output, configuration or run history before relying on it.
Feature coverage
- Documented Hermes task path (covered): Steps identify whether an action uses documented xCloud controls, upstream operator configuration or human review. Choose durable, safe conventions Locate the active profile and save the approved entry Inspect the active profile memory file Verify fresh-session loading Maintain the memory responsibly
- Task-specific acceptance check (covered): The final step validates this guide’s stated result. Maintain the memory responsibly