能力标签

🤖 Agent 🔄 工作流 🌐 翻译 💻 CLI 🔗 REST API 🖼 视觉 🔊 TTS 🎙 STT 🧠 Claude ✨ GPT

⚙️

Agent工作流

Hermes桌面版

基于 TypeScript · 无代码搭建完整 AI 自动化流程

英文名：hermes-desktop

⭐ 12.3k Stars 🍴 1.4k Forks 💻 TypeScript 📄 MIT 🏷 AI 8.5分

8.5AI 综合评分

aichatbottypescript

⬇ 下载源码 ZIP ⚙️ 配置说明 📺 TG 频道

✦ AI Skill Hub 推荐

AI Skill Hub 强烈推荐：Hermes桌面版是一款优质的Agent工作流。在 GitHub 上收获超过 12.3k 颗 Star，AI 综合评分 8.5 分，在同类工具中表现稳健。如果你正在寻找可靠的Agent工作流解决方案，这是一个值得深入了解的选择。

📚 深度解析

Hermes桌面版是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

Hermes桌面版工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.5 分，是同类 Agent 工作流中的精选推荐。

📋 工具概览

Hermes桌面版是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars

⭐ 12.3k

开发语言

TypeScript

支持平台

Windows / macOS / Linux

维护状态

活跃维护，更新频繁

开源协议

MIT

AI 综合评分

8.5 分

工具类型

Agent工作流

Forks

1.4k

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

可视化 Agent 工作流编排，无需编写复杂代码
支持多步骤自动化任务链，实现全流程无人值守
与外部 API、数据库和第三方服务无缝集成
内置错误处理与自动重试机制，保障稳定运行
提供可复用的自动化模板，快速在同类场景部署

🎯 主要使用场景

自动化日常重复性工作，将精力集中于创造性任务
构建数据采集 → 处理 → 输出的完整自动化管线
实现跨平台、跨系统的数据流转和业务协同

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：npm 全局安装
npm install -g hermes-desktop

# 方式二：npx 直接运行（无需安装）
npx hermes-desktop --help

# 方式三：项目依赖安装
npm install hermes-desktop

# 方式四：从源码运行
git clone https://github.com/fathah/hermes-desktop
cd hermes-desktop
npm install
npm start

📋 安装步骤说明

访问 GitHub 仓库获取工作流文件
在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
上传工作流文件
按照提示配置必要的环境变量和 API Key
运行测试确认流程正常后投入使用

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 命令行使用
hermes-desktop --help

# 基本用法
hermes-desktop [options] <input>

# Node.js 代码中使用
const hermes_desktop = require('hermes-desktop');

const result = await hermes_desktop.run(options);
console.log(result);

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

# hermes-desktop 配置说明
# 查看配置选项
hermes-desktop --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export HERMES_DESKTOP_CONFIG="/path/to/config.yml"

📑 README 深度解析真实文档完整度 58/100 查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

简介

<a href="README.md">English</a> · <a href="README.zh-CN.md">简体中文</a> · <a href="README.ja-JP.md">日本語</a> · <a href="README.es-LATAM.md">Español (LATAM)</a>

This project is in active development. Features may change, and some things might break. If you run into a problem or have an idea, open an issue. Contributions are welcome!

Hermes Desktop is a native desktop app for installing, configuring, and chatting with Hermes Agent — a self-improving AI assistant with tool use, multi-platform messaging, and a closed learning loop.

Instead of managing the CLI by hand, the app walks through install, provider setup, and day-to-day usage in one place. It uses the official Hermes install script, stores Hermes in ~/.hermes, and gives you a GUI for chat, sessions, profiles, memory, skills, tools, scheduling, messaging gateways, and more.

Features

Guided first-run install for Hermes Agent with progress tracking and dependency resolution
Local or remote backend — run Hermes locally on 127.0.0.1:8642, or connect the desktop app to a remote Hermes API server with URL + API key
Multi-provider support — OpenRouter, Anthropic, OpenAI, Google (Gemini), xAI (Grok), Nous Portal, Qwen, MiniMax, Hugging Face, Groq, and local OpenAI-compatible endpoints (LM Studio, Atomic Chat, Ollama, vLLM, llama.cpp)
Streaming chat UI with SSE streaming, tool progress indicators, markdown rendering, and syntax highlighting
Token usage tracking — live prompt/completion token counts and cost display in the chat footer, plus a /usage slash command
22 slash commands — /new, /clear, /fast, /web, /image, /browse, /code, /shell, /usage, /help, /tools, /skills, /model, /memory, /persona, /version, /compact, /compress, /undo, /retry, /debug, /status, and more
Session management — full-text search (SQLite FTS5), date-grouped history, resume and search across conversations
Profile switching — create, delete, and switch between separate Hermes environments with isolated config
14 toolsets — web, browser, terminal, file, code execution, vision, image gen, TTS, skills, memory, session search, clarify, delegation, MoA, and task planning
Memory system — view/edit memory entries, user profile memory, capacity tracking, and discoverable memory providers (Honcho, Hindsight, Mem0, RetainDB, Supermemory, ByteRover)
Persona editor — edit and reset your agent's SOUL.md personality
Saved models — CRUD management for model configurations across providers
Scheduled tasks — cron job builder (minutes, hourly, daily, weekly, custom cron) with 15 delivery targets
16 messaging gateways — Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Mattermost, Email (IMAP/SMTP), SMS (Twilio/Vonage), iMessage (BlueBubbles), DingTalk, Feishu/Lark, WeCom, WeChat (iLink Bot), Webhooks, Home Assistant
Hermes Office (Claw3d) — visual 3D interface with dev server and adapter management
Backup, import & debug dump — full data backup/restore and system diagnostics from Settings
Log viewer — view gateway and agent logs directly from the Settings screen
Auto-updater — check for and install updates via electron-updater
i18n ready — internationalization framework with English locale covering all screens, ready for community translations
Test suite — SSE parser, IPC handlers, preload API surface, installer utilities, and constants validation with Vitest

Prerequisites

Node.js and npm
A Unix-like shell environment for the Hermes installer
Network access for downloading Hermes during first-run install

Install dependencies

npm install

Install

Build the desktop app

npm run build

Platform packaging:

npm run build:mac
npm run build:win
npm run build:linux
npm run build:rpm    # Fedora/RHEL .rpm only

First-Time Setup

When the app opens for the first time, it will either detect an existing Hermes installation or offer to install it for you.

Supported setup paths in the UI:

OpenRouter
Anthropic
OpenAI
Local LLM via an OpenAI-compatible base URL

Local presets are included for:

LM Studio
Atomic Chat
Ollama
vLLM
llama.cpp

Hermes files are managed in:

~/.hermes
~/.hermes/.env
~/.hermes/config.yaml
~/.hermes/hermes-agent
~/.hermes/profiles/ — named profile directories
~/.hermes/state.db — session history database
~/.hermes/cron/jobs.json — scheduled tasks

~/.hermes/config.yaml

secrets: provider: command command: secret-tool lookup hermes "$HERMES_SECRET_KEY"


Or a helper that dumps a dotenv blob (e.g. a vault that unseals into tmpfs):

yaml secrets: provider: command command: "cat /run/user/1000/hermes-secrets.env" ```

The helper's stdout may be either a single bare value (per-key helpers) or KEY=VALUE lines (dotenv dumps); both shapes are auto-detected.

Tool Integrations

Exa Search, Parallel API, Tavily, Firecrawl, FAL.ai (image generation), Honcho, Browserbase, Weights & Biases, and Tinker.

Vault / secret manager integration (no TPM required)

The command provider is vault-agnostic — it runs whatever helper you configure and reads its stdout. The helper is the only thing that needs to talk to your secret store. If you don't have a TPM-sealed keyfile, any of these work without code changes to Hermes:

- KeePassXC (password-only DB, no keyfile): point secrets.command at a small kpxc-export.sh script that does keepassxc-cli ls ~/secrets/hermes.kdbx <<<"$KPXC_PASSWORD" and dumps the relevant group as dotenv. Prompt the user for the master password once per session. - GnuPG with a passphrase-only key: `gpg --batch --passphrase-fd 0 --decrypt ~/.keys/api-keys.gpg works directly as the command` value. Pass the passphrase via a file descriptor or env var, never argv. - pass (the standard unix password manager): command: "pass show hermes/$HERMES_SECRET_KEY" for a per-key helper, or a small wrapper script for a dotenv dump. - secret-tool (libsecret/Gnome Keyring): command: "secret-tool lookup hermes $HERMES_SECRET_KEY" (already shown above as the canonical per-key example). - Bitwarden CLI: bw get item "$HERMES_SECRET_KEY" | jq -r .notes (after bw unlock in the session). - 1Password CLI: op read "op://vault/$HERMES_SECRET_KEY/credential". - Plain env file with user-managed permissions: command: "cat ~/.config/hermes/secrets.env" with chmod 600 and the file owned by your user. Not as secure as a vault, but better than a world-readable .env.

The point: any helper that prints a value (per-key) or a dotenv blob (list-mode) on stdout will work, and Hermes imposes a 3-second timeout and 1 MiB output cap on the helper so a misbehaving one can't wedge the app. The provider makes no assumptions about TPM, FIDO2, smart cards, or platform keychains.

Security model:

- The command string is your own configuration — same trust level as .env. It runs via /bin/sh -c, so the command provider is POSIX-only (Linux/macOS); Windows stays on the env provider. - The helper inherits the process environment plus HERMES_SECRET_KEY; the key name is passed as data, never interpolated into the shell string. - Hard 3-second timeout (resolution is synchronous on the main process — keep helpers fast and non-interactive), 1 MiB output cap, and stderr is discarded. - Resolved values are never logged or written to disk; failures degrade to "key unset", logging only exit code/signal. - The gateway-spawn broadcast uses a single list() call, never a per-key helper loop.

Source of truth: src/main/secrets/.

🎯 aiskill88 AI 点评 A 级 2026-06-16

高质量的开源AI工作流项目