Book a demo
Book a demo
Login

Playbook Hermes Agent

Send a daily research briefing to Telegram

Test a self-contained research prompt, then schedule a Telegram briefing with explicit topics, source links and a clear failure path.

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

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

Illustrative scenario: a product team wants a weekday scan of official release and policy updates, with dated primary links for a quick morning read.

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

Confirm live research and scheduler prerequisites

Where
Hermes dashboard and authorized terminal/SSH if enabled
Permissions
Authorized Hermes administrator
Inputs
Running Gateway, working provider, working web search and configured Telegram target
Action
Check xCloud Status/Providers/Channels, confirm the Hermes Gateway is running, and test that the installed profile has working web search. Hermes’ daily-briefing tutorial uses a Firecrawl API key; xCloud does not document web search preconfigured, so verify the actual configured search tool.
Expected result
Gateway, provider and Telegram delivery are ready before scheduling.
Verify
Send a harmless manual Telegram test and confirm it arrives.
If it fails
If any prerequisite is missing, resolve that first; do not create a job that cannot deliver.

Sources: xCloud Hermes Agent deployment guide · Hermes daily briefing tutorial · Hermes cron feature guide

Step 2 of 5

Define daily source and freshness rules

Where
Team-approved briefing specification
Permissions
Research owner
Inputs
Two or three public topics, daily cutoff, primary-source rule, citation/output format
Action
Specify topics, the daily run cutoff, required primary-source pages, publication date and the time Hermes actually checked the pages. Request three findings with direct URLs, a fact/inference distinction and an explicit “no verified update” result.
Expected result
A reader can judge whether the result is complete and timely.
Verify
Have a recipient approve the format and source rules.
If it fails
If topics or time window are ambiguous, narrow them before scheduling.

Sources: Hermes daily briefing tutorial

Step 3 of 5

Run a manual source-retrieval test

Where
Hermes terminal or configured Telegram
Permissions
Authorized user
Inputs
One approved current topic; working web-search configuration
Action
Ask Hermes to find current public sources, open primary-source pages and return up to three findings with page date, retrieval time, direct URL and fact/inference labels. Require an explicit source/access gap if the configured search tool cannot complete the task.
Expected result
A draft report contains traceable links and clear uncertainty.
Verify
Open every cited primary source and check each claim against the page and its publication date.
If it fails
If sources are weak or inaccessible, ask Hermes to label gaps; do not fill them with invented claims.

Sources: Hermes daily briefing tutorial

Step 4 of 5

Schedule one weekday run

Where
Authorized Hermes terminal/CLI reached through the documented xCloud SSH route, if enabled
Permissions
Hermes operator authorized to create cron jobs
Inputs
Validated prompt; chosen time; configured Telegram home channel
Action
After checking the scheduler’s actual timezone, use the upstream form `hermes cron create "0 8 * * 1-5" "<validated research prompt>" --name "Weekday research briefing" --deliver telegram`. Verify the installed CLI/help syntax first; xCloud does not document a cron dashboard. The job uses a fresh context.
Expected result
A single scheduled research job is listed with the intended schedule and destination.
Verify
Inspect job list/configuration and verify its timezone, prompt and target.
If it fails
If the command/provider/delivery syntax differs from the installed version, stop and consult its current CLI help/docs.

Sources: Hermes cron feature guide

Step 5 of 5

Review the first delivery

Where
Telegram and Hermes cron run history
Permissions
Briefing owner
Inputs
First scheduled result and run status
Action
Inspect the first report and run record; compare claims to linked sources and check delivery destination.
Expected result
The recipient gets the agreed report or a visible failure status.
Verify
Record whether the job completed and whether the report met the contract.
If it fails
For a bad result, pause or edit the job and correct the prompt; do not create a duplicate schedule.

Sources: Hermes cron feature 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

  • First validate the research prompt manually. With Gateway and Telegram configured, an authorized operator can use `hermes cron create "0 8 * * 1-5" "<validated prompt>" --name "Weekday research briefing" --deliver telegram`. Then inspect `hermes cron list`, `hermes cron status`, `hermes cron runs` and actual delivery. Check scheduler timezone; xCloud does not document a cron 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