Hermes Agent

Hermes is the persistent background worker tier — an always-on, self-improving MCP bridge that runs 24/7 on the AI OS platform. While Claude is the "brain" (planning and decisions), Hermes is the "hands" (interacting with the real world around the clock).

Architecture

Hermes connects to AI OS as a Model Context Protocol (MCP) server. The Orchestrator delegates tasks to Hermes for persistent, background execution:

Claude (AI OS) — Planning, decision-making, orchestration, complex reasoning
Hermes — 24/7 execution, mobile bridge, cron jobs, approval gating, long-running tasks

The MCP connection is managed by the platform and configured automatically for each tenant.

Remote Approval Gate

When Hermes encounters a destructive or risky operation, it pauses execution and pushes an approval prompt to your phone:

A task requests a risky action (file deletion, force-push, database modification)
Hermes suspends the action and creates an approval request
A notification is sent via Telegram, Slack, or Discord
You approve or reject from your phone
Hermes resumes or aborts based on your decision

Approval requests are tagged with risk levels:

Risk Level	Examples	Default Action
High	Force-push, database drop, production deploy, key rotation	Block until approved
Medium	File deletion, config changes, branch deletion	Block until approved
Low	Log cleanup, cache purge, temp file removal	Auto-approve after 5 min

Walkaway Mode

Initiate a long-running task from the dashboard, then close your laptop. Hermes acts as the bridge:

Progress pings — Sends status updates to your phone at each milestone
Mobile replies — Reply from your phone with instructions: "keep going," "make it simpler," "push to GitHub"
Completion notification — Alerts you when the task finishes with a summary
Approval integration — If the task hits a risky action, you get an approval prompt on mobile

Example: Start a massive refactoring task, walk away, and Hermes will ping you on Telegram with progress updates. Reply "push to staging" from your phone when it's done.

Remote Bug Diagnosis

When a bug report arrives in Discord or Slack, use Hermes from your phone to trigger analysis:

Send a message to Hermes via Telegram: "Analyze the auth bug reported in #bugs"
Hermes reads the bug report, instructs Claude to analyze the relevant files
Claude's diagnosis is sent back to your phone
Optionally, approve a fix from mobile

24/7 Cron Jobs

While AI OS requires your environment to be open, Hermes runs persistently. Delegate scheduled tasks that execute automatically:

Job	Schedule	Description
Inbox Summary	`0 8 * * *`	Daily email digest pushed to Telegram
AI News Brief	`30 7 * * 1-5`	Weekday morning AI/tech roundup
GitHub Backup	`0 2 * * *`	Nightly repository backup to secondary location
Comment Monitor	`0 /4 * *`	YouTube/social comment tracker every 4 hours
Health Check	`/30 * * *`	Platform health, memory, and service monitoring

Self-Improving Skills

Hermes has an autonomous "do, learn, improve" loop. When it solves a complex problem, it extracts the successful patterns and writes them into reusable skill files for faster future execution. These skills are stored on the platform and available to all agents in your tenant.

API Endpoints

GET /api/hermes/status

Check MCP connection status, uptime, stats, and loaded skills.

POST /api/hermes/delegate

Delegate a task to Hermes. Modes: background, walkaway, or cron.

GET /api/hermes/tasks

List all active delegated tasks with progress and logs.

GET /api/hermes/approvals

Get pending approval requests with risk levels and context.

POST /api/hermes/approvals/:id

Approve or reject a pending action. Body: { "decision": "approve" }

GET /api/hermes/cron

List all scheduled Hermes cron jobs.

POST /api/hermes/cron

Create a new Hermes cron job.

Configuration

Variable	Default	Description
`HERMES_MCP_URL`	`http://127.0.0.1:8420`	MCP server endpoint for Hermes
`TELEGRAM_BOT_TOKEN`	—	Required for mobile approval prompts via Telegram
`SLACK_WEBHOOK_URL`	—	Required for Slack notifications from Hermes

Key Benefits

Tenant isolation — Each tenant's Hermes tasks are fully isolated from other tenants.
Cost efficiency — Background and cron tasks use your own API keys at standard rates.
Always available — Unlike interactive sessions, Hermes works 24/7 without requiring your browser.

← Notifications