Book a demo
Book a demo
Login

Playbook Hermes Agent

Update or roll back the Hermes version in xCloud

Check the current version, apply an xCloud dashboard update during an agreed window, validate one core task and use documented pin or rollback controls only if needed.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

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.

    xCloud Hermes Agent deployment guide

  • Confirm the managed Hermes service is running and use only xCloud controls documented for this task; any upstream Hermes CLI, file or scheduled-job procedure needs an authorized operator and is not evidence of an xCloud panel feature.

    xCloud Hermes Agent deployment guide

Illustrative situation

Illustrative scenario: an administrator plans an agent version update and needs a functional baseline plus an available version rollback control.

Choose the approach

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

Establish a working baseline

Where
Hermes dashboard → Status and Updates, then current terminal/Telegram path
Permissions
Authorized Hermes administrator and task owner
Inputs
Current version, harmless known request, expected response/delivery
Action
Record the running version and complete a known harmless task before the change. Save the observed response/delivery and choose an agreed maintenance window.
Expected result
The operator knows the current version and expected interruption.
Verify
Confirm an owner is available to test the service afterward.
If it fails
If current version or update state cannot be identified, defer the change.

Sources: xCloud Hermes Agent deployment guide

Step 2 of 5

Confirm rollback control

Where
Hermes dashboard → Updates
Permissions
Authorized Hermes administrator
Inputs
Current dashboard options
Action
Inspect the available pin/rollback controls and note the documented recovery option before updating.
Expected result
A current rollback option is visible or its absence is understood.
Verify
Do not claim a prior version is restorable unless the dashboard offers it for this instance.
If it fails
If there is no suitable rollback option, assess impact and obtain owner approval before update.

Sources: xCloud Hermes Agent deployment guide

Step 3 of 5

Apply the update

Where
Hermes dashboard → Updates
Permissions
Authorized Hermes administrator
Inputs
Approved window; confirmed current version
Action
Open the target Hermes server’s Updates panel, inspect the current and offered versions, read the xCloud update notes shown for this instance, and select the visible update control once. Wait for the dashboard to report completion before starting the post-update task.
Expected result
xCloud reports that the selected update completed and shows the resulting version.
Verify
Recheck the running version and Status panel, then inspect Logs for update errors before testing the task.
If it fails
If update fails or hangs, do not repeat blindly; inspect logs and use xCloud’s documented recovery path.

Sources: xCloud Hermes Agent deployment guide

Step 4 of 5

Compare the same task after update

Where
Hermes terminal or configured Telegram channel
Permissions
Authorized Hermes user
Inputs
Same harmless request and expected response/delivery from baseline
Action
Repeat the exact supplied-text task and compare response and delivery to the recorded baseline. A version rollback only changes the selected Hermes version; it is not a data restore.
Expected result
Agent response and delivery still meet the pre-update acceptance check.
Verify
Compare against the saved baseline and inspect update logs.
If it fails
If core workflow regresses, capture the error and decide whether the visible version rollback is appropriate; preserve separate data recovery planning.

Sources: xCloud Hermes Agent deployment guide

Step 5 of 5

Roll back only if needed

Where
Hermes dashboard → Updates → rollback/pin controls
Permissions
Authorized Hermes administrator
Inputs
Observed regression, current and target version
Action
If the test shows a material regression, use the version rollback/pin action available in xCloud, then re-run the core workflow.
Expected result
Dashboard confirms the chosen version state.
Verify
Verify running version, status and core task after rollback.
If it fails
If the desired version is unavailable, stop and contact xCloud support; do not improvise shell downgrade steps.

Sources: xCloud Hermes Agent deployment guide

Maintenance

Recovery decisions

  • If a regression appears, use the visible xCloud rollback/pin option only if available, then rerun the core task; otherwise contact xCloud support.

    xCloud Hermes Agent deployment guide

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

Copyable agent brief

Manual checkpoints

  • An authorized administrator uses the documented Hermes Updates panel. A version rollback is separate from restoring agent data.
  • Review the task-specific acceptance check and inspect actual output, configuration or run history before relying on it.
Feature coverage

Sources

Continue

Review xCloud Hermes deployment options