What Hermes can connect to and do
32 capability and integration records: what each is for, what you need, how to set it up, how to check it works, and where it stops.
Capabilities 13Integrations 8Messaging platforms 4Models & providers 4Other 3
Capabilities13 records
- SkillsPackage a successful procedure so Hermes can load the relevant instructions when a similar task returns.
- PluginsExtend Hermes with custom tools, hooks, and integrations when instructions alone cannot supply the needed capability.
- Scheduled tasksRun bounded tasks on a schedule and retain separate evidence of execution, useful output, and delivery.
- Persistent memoryRetain stable preferences and environment facts across sessions while keeping detailed evidence in durable project records.
- Context filesKeep project rules, conventions, and operating boundaries in files that Hermes can discover from the working directory.
- Browser toolsUse a configured browser backend for navigation, visible page interaction, forms, and tasks requiring an authenticated session.
- Web search and extractionDiscover pages and retrieve readable source content with a configured backend, keeping search results distinct from verified evidence.
- Voice and TTSChoose a text-to-speech and speech-to-text provider so Hermes can talk back and understand voice messages.
- Subagent delegationUse the delegate_task tool to hand pieces of work to isolated child agents that run in parallel and report back.
- Code executionThe execute_code tool lets Hermes write and run a Python script that calls its own tools, collapsing many steps into one.
- Checkpoints and rollbackSnapshot your working directory before Hermes edits files, then preview or restore earlier states with /rollback.
- Command approvalsControl how Hermes handles dangerous shell commands with smart, manual or off approval modes, deny patterns and a hardline blocklist.
- Terminal backendsRun the agent's shell commands locally, in Docker, on a remote host over SSH, or in cloud sandboxes like Modal, Daytona and Vercel Sandbox.
Integrations8 records
- MCPExpose selected tools from a local or remote MCP server to Hermes without building a native tool first.
- TelegramUse Telegram as a conversation and delivery surface while keeping bot credentials and allowed users explicitly controlled.
- DiscordConnect Hermes to direct messages or server channels with deliberate mention rules, authorization, and session boundaries.
- GitHubBuild repository research and review workflows through documented GitHub CLI or separately configured MCP routes.
- Google WorkspaceUse the documented Workspace skill route for Gmail, Calendar, Drive, Sheets, Docs, and related account data.
- Home AssistantInstall the official homeassistant plugin to give Hermes smart-home tools and react to entity state changes.
- API serverExpose Hermes as an OpenAI-compatible HTTP endpoint so chat frontends and scripts can talk to your agent.
- IDE integration (ACP)Start Hermes in Agent Client Protocol mode so editors like VS Code, Zed and JetBrains IDEs can use it as a coding agent.
Messaging platforms4 records
- SlackConnect Hermes to Slack over Socket Mode so allowed teammates can message it in DMs, channels and threads.
- WhatsAppLink Hermes to WhatsApp as a linked device through a bundled Node.js bridge, in bot or self-chat mode.
- SignalTalk to Hermes over Signal by linking signal-cli as a secondary device and pointing the gateway at its local HTTP daemon.
- Email gatewayLet Hermes read a dedicated mailbox over IMAP and reply over SMTP, with sender authentication on by default.
Models & providers4 records
- Models and providersUnderstand which model handles conversation and which auxiliary models handle supporting tasks before diagnosing quality or cost.
- Image generationPick an image backend such as FAL.ai, OpenAI, OpenRouter, xAI or Krea so the agent can generate images on request.
- External memory providersAdd one external memory backend, such as Honcho, Mem0, Hindsight or Supermemory, on top of Hermes's built-in memory.
- Fallback providersDefine a chain of backup model providers that Hermes switches to on rate limits, outages or auth errors.
Other3 records
- DeploymentUnderstand the difference between running Hermes in a container and using a container only for terminal commands.
- CLIUse the terminal interface for interactive work, bounded single queries, explicit tool selection, and resumable sessions.
- DesktopUse the native desktop interface to work with the same Hermes core, sessions, configuration, skills, and memory.
No tools match that filter.
Official and community resourcesExternal, for discovery
- Official Hermes documentation Documentation · The authoritative starting point for supported features, installation, and configuration.
- Official community stories Use cases · Reported examples from people using Hermes. A discovery source, not proof that every workflow will reproduce.
- Hermes source and releases Repository · Inspect source changes, release notes, and issue discussions when a guide depends on a particular version.
- Agent Use Cases Use cases · Discover examples across several agents, with links back to their original reports. Cross-agent examples need a separate Hermes compatibility check.
External resources are listed for discovery. Inclusion is not a compatibility, security or quality certification. No paid placements or affiliate links.