Doc Pack Needs human review

Doc Pack: Stable server Docker or dedicated Mac mini

Help AI plan a stable long-running Hermes setup using either server + Docker-oriented operations or a dedicated Mac mini with explicit operational controls.

Expected outcome

AI helps the user choose the stable host model, document operations, verify security/update behavior, and run a real use case with a recovery plan.

Source status: official-sources-verified-editorial-recommendation-needs-review

Copy into AI

Prompt to start with

Human review first

I want a stable long-running Hermes setup. I am choosing between server + Docker-oriented operations and a dedicated Mac mini. Use official Hermes configuration, security, updating, tools, and messaging sources first. Treat the final environment choice as Hermes Agent Hub editorial guidance, not an official Nous requirement. Before implementation, help me decide based on uptime, remote access, backup, logs, update workflow, approval mode, gateway exposure, and rollback expectations.

Use this as the starting instruction. Then attach or link the documents listed below. Do not let AI invent unsupported requirements.

How to use

Use this Doc Pack before commands

Start by choosing server + Docker or dedicated Mac mini; do not mix both as the first stable target.
Attach official configuration, security, updating, tools, and messaging sources.
Ask AI to write an operations runbook before adding real workloads.
Run one real use case and verify restart, logs, access control, and backup assumptions.

Guardrails

Keep AI inside these limits

Do not call the environment stable until restart and recovery have been tested.
Do not enable messaging gateways or remote control without allowlists and pairing rules.
Do not let AI optimize for convenience at the expense of security approvals.

Preflight

Questions AI must ask first

Is the target environment server + Docker/SSH, dedicated Mac mini, or both?
What uptime, remote access, and backup expectations are required?
Which approval mode should be used and why?
Will messaging gateway access be enabled, and who is allowlisted?
What is the update and rollback workflow?

Verification

Definition of done

The chosen backend and security mode are explicitly documented.
Update, doctor, logs, restart, and gateway checks are documented.
A backup/snapshot or rollback point exists before gateway exposure.
The user can explain when to prefer server + Docker and when to prefer Mac mini.

Last reviewed: 2026-04-21

Source bundle

Documents to attach or verify

Official sources are separated from Hermes Agent Hub editorial checklists so AI can reason with the right level of confidence.

Required Verified source official

Official configuration guide

Verify terminal backends, Docker/SSH options, approvals, and checkpoints.

Primary source for stable backend and safety-mode configuration; do not treat Docker as only a visual deployment detail.

Required Verified source official

Official security guide

Require authorization, approval modes, isolation, and input-safety decisions before long-term exposure.

Required for any server, messaging gateway, or long-running deployment recommendation.

Required Verified source official

Official updating guide

Define update and post-update validation expectations for a long-running instance.

Required for any stable or long-running deployment recommendation.

Optional Verified source official

Official tools and toolsets guide

Connect stable deployment to real tool use, cron jobs, delegation, and terminal backend decisions.

Use to connect deployment choices to actual post-install capabilities.

Optional Verified source official

Official messaging gateway guide

Use only after the base deployment works; review allowlists and pairing before connecting chat platforms.

Use only after the base deployment works; gateway setup increases security and account-management responsibilities.

Required Needs human review manual

V1 stable operations checklist

Editorial checklist for backups, logs, restarts, monitoring, gateway access, updates, and rollback.

This combines official safety sources with V1 operational guidance; it should be reviewed before being shown as a final recommendation.

Supporting sources

All linked resources

official Verified source

Official installation guide

Official install path for Linux, macOS, WSL2, and Android Termux. Use this before asking AI to run install commands.

Review note: Confirms the one-line installer, supported operating systems, Git prerequisite, installer-managed dependencies, and post-install verification commands.

official Verified source

Official configuration guide

Official configuration page covering terminal backends such as local, Docker, SSH, Modal, Daytona, and Singularity, plus approval modes and checkpoints.

Review note: Primary source for stable backend and safety-mode configuration; do not treat Docker as only a visual deployment detail.

official Verified source

Official security guide

Official defense-in-depth guide covering user authorization, dangerous command approval, container isolation, credential filtering, context scanning, session isolation, and input sanitization.

Review note: Required for any server, messaging gateway, or long-running deployment recommendation.

official Verified source

Official updating and uninstalling guide

Official guide for hermes update and post-update validation such as hermes doctor, version checks, gateway status, and dependency checks.

Review note: Required for any stable or long-running deployment recommendation.

manual Needs human review

V1 editorial stable operations checklist

Hermes Agent Hub editorial checklist for long-term operation: updates, backups, logs, restarts, gateway allowlists, approval modes, and rollback expectations.

Review note: This combines official safety sources with V1 operational guidance; it should be reviewed before being shown as a final recommendation.

official Verified source

Official tools and toolsets guide

Official guide to built-in tools, terminal backends, browser automation, memory, delegation, cron, messaging delivery, integrations, and toolset configuration.

Review note: Use to connect deployment choices to actual post-install capabilities.

official Verified source

Official messaging gateway guide

Official gateway guide for Telegram, Discord, Slack, WhatsApp, Signal, SMS, Email, Matrix, Feishu/Lark, WeCom, and other platforms, including allowlist security.

Review note: Use only after the base deployment works; gateway setup increases security and account-management responsibilities.

official Verified source

NousResearch/hermes-agent GitHub repository

Official source repository for Hermes Agent. Use it to verify current install scripts, README, issues, source tree, and update state.

Review note: Verify repository state before copying install, update, or troubleshooting steps.

manual Needs human review

V1 editorial Mac mini checklist

Hermes Agent Hub editorial checklist for power, network, remote access, logs, restart behavior, disk space, and backup planning on a Mac mini.

Review note: This is a V1 editorial recommendation, not an official Nous Research requirement.

official Verified source

Official persistent memory guide

Official memory guide covering MEMORY.md, USER.md, session search, duplicate prevention, and security scanning for memory entries.

Review note: Useful when explaining why a long-running Hermes instance can become more valuable over time.

official Verified source

Official skills system guide

Official skills guide. Skills are on-demand knowledge documents and slash commands stored under ~/.hermes/skills/.

Review note: Useful for the first post-install activation flow.