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.
For a new install, choose credentials in the live deployment form before creating the server; for existing-server procedures, confirm the managed Hermes service is running. Use only documented xCloud controls; upstream CLI/config requires an authorized operator.
Illustrative situation
Illustrative scenario: a new xCloud Hermes owner has chosen a provider and wants to verify the service with a short supplied paragraph before connecting business data.
Choose the approach
Choose an available provider in the xCloud deployment form and use terminal/SSH or the configured Telegram path for the first test. Do not proceed if the target provider is absent from the live form.
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Choose an eligible server and provider
- Where
- xCloud dashboard → Create managed server → Web server: Agentic → Hermes Agent
- Permissions
- xCloud account and provider account owners
- Inputs
- Current eligible size/region, currently listed provider and provider credential
- Action
- Review the live deployment form, select a listed server meeting xCloud’s documented 4GB minimum, then choose a currently listed provider and prepare its credential for the form. Confirm region, plan and optional backup choice.
- Expected result
- The deployment form accepts the selected server and shows the cost and configuration before launch.
- Verify
- Verify the selected server and expected charge in the review screen.
- If it fails
- If no eligible size is shown, stop and check current xCloud requirements; do not infer an alternative size.
Sources: xCloud Hermes Agent deployment guide
Step 2 of 5
Deploy Hermes with the provider
- Where
- xCloud deployment form
- Permissions
- Authorized server owner and provider account owner
- Inputs
- Selected server/provider; provider credential; security acknowledgement
- Action
- Enter the selected provider credential in the deployment form, review the security acknowledgement, and submit the xCloud deployment.
- Expected result
- The Hermes server appears in the xCloud dashboard with deployment status.
- Verify
- Wait for a ready status and record the server identity.
- If it fails
- If deployment fails or remains pending, use xCloud deployment status/logs or support; do not repeat creation blindly.
Sources: xCloud Hermes Agent deployment guide
Step 3 of 5
Verify provider configuration
- Where
- Hermes server → Providers
- Permissions
- Authorized Hermes administrator
- Inputs
- Provider selected during deployment
- Action
- Open Providers and confirm the selected provider is active. Do not paste the secret into chat or a report.
- Expected result
- The dashboard shows the expected provider.
- Verify
- Compare it with the provider selected in the deployment form.
- If it fails
- If the provider is missing, inspect deployment status/logs and use the documented provider panel only after the instance is ready.
Sources: xCloud Hermes Agent deployment guide
Step 4 of 5
Choose an access path
- Where
- Hermes dashboard → SSH Access, or configured Telegram channel
- Permissions
- Authorized server owner; Telegram owner if using Telegram
- Inputs
- SSH access or already-configured Telegram
- Action
- Use the terminal/SSH route or connect a provider and use the configured messaging channel. The hosted Hermes dashboard itself has no chat box.
- Expected result
- A usable Hermes interface is available through the chosen route.
- Verify
- Confirm you are on the intended server/account before sending a test.
- If it fails
- If neither interface is ready, inspect dashboard status and channel setup; do not assume a chat panel exists.
Sources: xCloud Hermes Agent deployment guide
Step 5 of 5
Run a harmless first task
- Where
- Hermes terminal/CLI or configured Telegram conversation
- Permissions
- Authorized user; avoid privileged or external actions
- Inputs
- A simple bounded request, such as summarizing supplied text
- Action
- Ask Hermes to summarize a short supplied paragraph and request a concise result with no external action.
- Expected result
- Hermes returns a relevant summary based only on the supplied text.
- Verify
- Compare the summary against the paragraph and verify no external action was requested or performed.
- If it fails
- If it fails, inspect provider/channel status and logs, then correct the specific setup issue before retrying.
Sources: Hermes quickstart · xCloud Hermes Agent deployment guide
Maintenance
Review provider credential ownership and the selected access path when staff or provider accounts change.
Recovery decisions
If the first task fails, inspect xCloud status/provider/channel logs, correct the specific issue and retry only the harmless test.
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
- Operate documented Hermes controls in the xCloud dashboard dashboard · manual
Manual xCloud interface. Use only deployment, Providers, Channels, Workspace and Updates controls documented by xCloud; do not infer extra dashboard capabilities.
Checkpoint: Confirm the intended Hermes server and current visible control before saving a change.
xCloud Hermes Agent deployment guide · xCloud Telegram setup for Hermes · xCloud Hermes Workspace setup guide
- 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
- Run the first harmless task through the verified terminal or Telegram path after provider setup. xCloud’s Hermes dashboard has no chat box.
- 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 an eligible server and provider Deploy Hermes with the provider Verify provider configuration Choose an access path Run a harmless first task
- Task-specific acceptance check (covered): The final step validates this guide’s stated result. Run a harmless first task
Sources
- xCloud Hermes Agent deployment guide
- Hermes quickstart
- xCloud Telegram setup for Hermes
- xCloud Hermes Workspace setup guide
- 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