Book a demo
Book a demo
Login

Playbook Hermes Agent

Change the Hermes model provider from xCloud

Use the documented Hermes Providers controls to change to a currently listed provider, validate a harmless task and retain a known configuration reference if available.

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 · Hermes quickstart

  • 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 · Hermes quickstart

Illustrative situation

Illustrative scenario: a provider owner has approved a model account change and wants a safe before/after check plus a verified fallback option.

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

Record the current provider and candidate rollback

Where
Hermes dashboard → Providers
Permissions
Authorized Hermes administrator
Inputs
Current provider name, current credential still available/authorized, target live choice, exact harmless test paragraph
Action
Before changing anything, use the current provider to summarize a short supplied paragraph; save the exact input and observed output. Record the current provider and verify its credential is still authorized. Then confirm the target provider is on the live xCloud list.
Expected result
A working before-change response and a selectable prior provider/credential are recorded before the change.
Verify
Confirm the harmless summary completed and the prior provider still appears in current choices; do not record its secret.
If it fails
If it is missing, stop; broad upstream compatibility does not prove xCloud supports it.

Sources: xCloud Hermes Agent deployment guide

Step 2 of 5

Prepare credential securely

Where
Provider console and approved secret manager
Permissions
Provider account owner
Inputs
Provider credential and rotation owner
Action
Create or select a provider credential with only the access needed, store it securely and avoid placing it in prompts or tickets.
Expected result
Credential is available for secure dashboard entry.
Verify
Check that the intended account and billing owner are correct.
If it fails
If credential scope or billing is unclear, resolve with provider owner first.

Sources: xCloud Hermes Agent deployment guide

Step 3 of 5

Change provider in xCloud

Where
Hermes dashboard → Providers → Change Provider
Permissions
Authorized Hermes administrator
Inputs
Selected live provider and credential
Action
In the Hermes server dashboard, open Providers → Change Provider, choose the approved live option, enter its credential in the protected form, and select Save Changes. Do not paste the key into chat, prompt, or report.
Expected result
The dashboard saves the target provider while keeping the credential out of task output.
Verify
Reopen Providers and confirm the selected provider name; never reproduce the key.
If it fails
If save fails, inspect status/logs and do not repeatedly paste the key.

Sources: xCloud Hermes Agent deployment guide

Step 4 of 5

Test a harmless request

Where
Hermes terminal or configured Telegram channel
Permissions
Authorized Hermes user
Inputs
The exact same supplied paragraph and response format used before the change
Action
After the dashboard change is saved, submit the exact same paragraph to Hermes and request the same concise summary format. Compare answer quality and response path with the saved before-change result.
Expected result
Hermes returns a coherent answer through the chosen model path.
Verify
Compare the same input/output criteria and confirm Hermes responds through the intended access path.
If it fails
If it fails, record the exact error and use the provider dashboard workflow to correct configuration.

Sources: xCloud Hermes Agent deployment guide

Step 5 of 5

Keep a rollback reference

Where
Approved operator runbook and dashboard
Permissions
Provider owner
Inputs
Previously used provider config if available
Action
Record the former provider name and the documented steps to reselect it; do not assume secrets or complete config are backed up.
Expected result
Operator knows how to return to a known provider choice if it remains available.
Verify
Verify the old option is currently selectable before treating it as a rollback path.
If it fails
If it is not available or key is unavailable, contact the provider owner; do not claim a guaranteed rollback.

Sources: xCloud Hermes Agent deployment guide

Maintenance

Recovery decisions

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 Providers panel. Hermes task prompts do not grant access to that xCloud dashboard.
  • 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