+
+
← Back to Derez.ai
+
+
Hermes Agent Setup Guide: From Zero to Your First AI Agent
+
+
+ Tutorial
+ Hermes Agent
+ June 10, 2026
+ · 6 min read
+
+
+
Hermes Agent (by Nous Research) is an open-source AI agent framework that turns any Linux server into an autonomous digital worker. It reads files, runs shell commands, writes code, manages background processes, and follows chronological schedules — all through a natural language persona that you define.
+
+
In this guide, you'll go from a blank server to a running Hermes agent with custom skills, a configured persona, and automated cron jobs. No manual SSH required — the Derez.ai dashboard handles provisioning, so you start at the good part.
+
+
What You'll Need
+
+
+ - A Derez.ai account ($4.99/mo with first-month coupon codes)
+ - An OpenRouter API key (or any OpenAI-compatible provider)
+ - About 10 minutes
+
+
+
Step 1: Provision Your Agent Instance
+
+
From the Derez.ai dashboard at app.derez.ai, click Create Agent. The platform spins up a dedicated Linux instance pre-configured with Python 3.11, the Hermes runtime, and all dependencies. You'll receive:
+
+
+ - Full SSH access (root) to your instance
+ - A dashboard URL for the Hermes web UI
+ - Automatic daily backups with 7-day retention
+ - Automatic SSL/TLS certificates
+
+
+
Provisioning takes about 60 seconds. When the status changes to Running, you're ready.
+
+
+ 💡 Pro tip: Use coupon code friends950 or creator950 at signup to get your first month for $0.50 — a full $9.50 discount.
+
+
+
Step 2: Configure Your Agent Persona
+
+
The agent persona is the single most important file in Hermes. Located at ~/.hermes/AGENT_PERSONA.md, it defines the agent's identity, tone, and behavioral rules. Every message the agent sends is shaped by this file — it's not just a system prompt, it's the agent's operating charter.
+
+
Here's a simple persona for a customer success agent:
+
+
+ AGENT_PERSONA.md
+ You are Mark, a Customer Success Agent for Derez.ai.
+ - You are helpful, concise, and proactive.
+ - You monitor new signups and send welcome messages.
+ - You check server health daily and flag issues.
+ - You speak like a knowledgeable colleague, not a robot.
+ Tool-use rules:
+ - Always verify before acting — double-check destructive commands.
+ - Use terminal for shell commands, process for background tasks.
+ - When blocked, report the blocker — never fabricate results.
+
+
+
You can edit this file directly from the Derez.ai dashboard's file manager, or via SSH. The agent reloads it on each conversation turn, so changes take effect immediately.
+
+
Step 3: Install Skills
+
+
Skills are the agent's capabilities — they extend what it can do. Skills live in ~/.hermes/skills/ and are plain Markdown files with structured frontmatter and tool-calling instructions.
+
+
To install a skill, create a file in the skills directory:
+
+
# ~/.hermes/skills/server-health.md
+
+---
+name: server-health
+description: Monitor server health metrics and alert on anomalies
+---
+
+You are an SRE assistant. Check these metrics daily:
+1. Disk usage — alert above 80%
+2. Memory usage — alert above 85%
+3. Load average — investigate if > 4.0
+4. Uptime — report days since last reboot
+5. Failed SSH logins — flag brute-force attempts
+
+Report findings in a single summary block. Escalate critical issues.
+
+
Hermes scans the skills directory at startup. Each skill file becomes available as a command the agent can invoke contextually. You can also load a skill mid-conversation with skill_view(name='server-health') — a powerful pattern for pulling in specialized knowledge on demand.
+
+
Step 4: Set Up Cron Jobs
+
+
One of Hermes' most powerful features is its built-in cron scheduler. Instead of writing crontab entries manually, you register schedules that wake the agent at specific times to perform tasks autonomously.
+
+
Cron jobs live in ~/.hermes/cron/ as YAML files:
+
+
# ~/.hermes/cron/daily-health-check.yaml
+
+schedule: "0 6 * * *" # Every day at 06:00
+skill: server-health
+output: report # Send result as a report
+
+---
+
+# ~/.hermes/cron/weekly-backup-report.yaml
+
+schedule: "0 9 * * 1" # Every Monday at 09:00
+skill: backup-verification
+output: report
+notify_on_complete: true # Get notified when done
+
+
The agent wakes at the scheduled time, loads the specified skill, runs the task, and reports back. This works even while your agent is in the middle of other conversations — Hermes handles concurrent execution gracefully.
+
+
Step 5: Test Your Agent
+
+
Open the Hermes web UI (available from your Derez.ai dashboard) and start a conversation. Try these test prompts:
+
+
+ - "What's my server health look like today?"
+ - "Check which cron jobs are scheduled and show me the next 3 runs."
+ - "List all installed skills and describe what each one does."
+ - "Run a quick disk usage check and tell me if anything needs attention."
+
+
+
The agent will reference its persona, load the relevant skills, and execute the appropriate tools — all in one response. You can watch it run commands live in the terminal output panel.
+
+
Going Further
+
+
Once the basics are running, here's what you can layer on:
+
+
+ - Plugins — Drop Python scripts into
~/.hermes/plugins/ for custom tool integrations (databases, APIs, webhooks)
+ - Memories — Persistent knowledge stored in
~/.hermes/memories/ that survives conversation resets
+ - Profiles — Multiple agent configurations (
~/.hermes/profiles/<name>/) that you can switch between for different roles
+ - Background processes — Launch long-running tasks (web scrapers, data pipelines, monitoring loops) that the agent manages independently
+
+
+
+
🔗 Related: See our
Speed Run: Odoo Community Agent tutorial for a real-world example — connecting Hermes to an Odoo database and pulling leads automatically.
+
+
+
Troubleshooting
+
+
Agent not responding
+
Check that the agent process is running: ps aux | grep hermes. From the Derez.ai dashboard, you can restart the agent with one click.
+
+
Skills not loading
+
Verify the file is in the correct directory (~/.hermes/skills/) with .md extension. Check the YAML frontmatter is valid — missing --- delimiters will silently skip the file.
+
+
Cron jobs not firing
+
Make sure the Hermes process that manages cron (typically hermesd) is running as a background service. Check with process(action='list') from the agent, or verify the service status from the dashboard.
+
+
Tool errors
+
If the agent reports tool execution failures, check the system dependencies listed in your skill files. The agent will tell you exactly which command failed and why — it never silently drops errors.
+
+
+
Ready to build your agent?
+
Get a dedicated Hermes agent instance with full SSH access, automatic backups, and a managed dashboard — starting at $0.50 for your first month.
+
Create Your Agent →
+
+
+