Chatbot
Waits for a prompt
Answers in a chat
Often starts fresh
Limited business-system access
Resource guide
Hermes Agent is an open-source AI agent built by Nous Research. Unlike a chatbot that mostly answers one prompt at a time, Hermes is designed as a persistent assistant: it can use tools, remember useful context, create reusable skills, run scheduled work, and connect to where you already communicate.
For a business, the important idea is simple: Hermes Agent can become the technical foundation for a private AI assistant across email, files, reports, databases, and business tools.
User
Memory
Context
Tools
Actions
Skills
Procedures
Files
CRM
Reports
Database
Browser
Calendar
Docs
Spreadsheets
Draft replies
Find answers
Prepare reports
Track follow-ups
Suggest recurring workflows
Quick answer
Carries useful context across sessions
Uses tools to inspect files, search the web, automate browsers, and run commands
Turns repeatable procedures into reusable skills
Runs scheduled tasks and recurring workflows
Connects to chat, email, and command-line interfaces
Can be self-hosted or deployed in a private environment
Plain English
Most people first experience AI through a chat window. You ask a question, the model replies, and the conversation ends. That is useful, but a business owner often needs follow-through: context checked, drafts prepared, recurring updates handled, and useful patterns remembered.
Hermes Agent is built for that more persistent kind of work. It is an AI agent, which means it is not limited to generating text. It can use tools, inspect files, search information, query external services, run scheduled tasks, and continue improving the way it handles repeated workflows.
The most important difference is that Hermes is designed to grow with use. When it solves a task, it can preserve what worked as a reusable skill. When it learns useful details about a user, project, or environment, it can carry that context into future work. Over time, the goal is not just to answer prompts better. The goal is to become better at the recurring work that matters to the person or business using it.
For a technical user, Hermes Agent is an open-source AI agent that can be installed, configured, extended, and self-hosted.
Waits for a prompt
Answers in a chat
Often starts fresh
Limited business-system access
Uses tools
Remembers context
Runs scheduled workflows
Works across business software
Why it matters
The attention is not just about one more chat interface. Hermes is built around memory, reusable skills, tool use, scheduled work, and multiple ways to reach the same assistant.
Hermes is designed so useful context can persist beyond a single conversation. Its built-in memory files let the agent keep notes about the user, projects, environments, and recurring workflows. That matters because repeated work usually depends on small details such as preferences, account names, file locations, business rules, and previous decisions. Instead of asking the user to restate all of that every time, Hermes can bring relevant context forward when it is helpful. The result is an assistant that starts closer to the real operating picture instead of treating each session as isolated.
Hermes can turn successful procedures into reusable skill documents defined by the Agent Skills specification. A skill can describe how to complete a specific kind of task, which tools to use, what checks matter, and what output format is expected. That gives the agent a practical way to reuse what worked instead of rediscovering the same process from scratch. It also makes improvement more inspectable, because the useful procedure can be read, edited, and refined over time. For recurring business work, this is often more valuable than a one-off answer that disappears after the chat ends.
Hermes is not limited to writing text in response to a prompt. Depending on how it is configured, it can use tools for web search, file operations, terminal commands, browser automation, vision, image generation, text-to-speech, and external integrations. Toolsets and individual tool toggles let a deployment expose only the tools needed for a given platform, session, or scheduled job. That lets it work with the systems where the relevant information already lives. It can inspect inputs, gather context, prepare an output, and leave a human with something concrete to review. The practical distinction is that the assistant can participate in a workflow rather than merely comment on it.
Hermes includes scheduled work through its cron system. That means some tasks can run at a chosen time or on a recurring cadence instead of waiting for a user to send a new prompt. A scheduled job might prepare a daily summary, a weekly report, an inbox check, an audit, or a monitoring update. The output can then be delivered through the configured interface, such as a messaging platform. This matters for operational work because many useful tasks are valuable precisely because they happen reliably before someone remembers to ask.
Hermes can expose the same assistant through more than one interface. Its gateway process connects the agent to messaging platforms and other frontends, depending on which adapters are configured. That can include chat platforms, email, command-line usage, and other supported entry points. The advantage is that the assistant can meet the user where the work already starts instead of forcing every request through a separate web chat. That keeps memory, skills, and context connected across entry points instead of creating separate assistants for each channel. For a private deployment, that flexibility can make the system feel less like a new destination and more like an added capability inside existing routines.
How it improves
The most useful way to understand Hermes Agent is as a loop. A normal AI chat often ends when the response is delivered. Hermes is designed to carry useful context and repeatable procedures from one session to the next.
This does not mean the agent becomes magically perfect. It still needs clear permissions, careful workflow design, good source data, and human review for important decisions. But it is designed for ongoing, context-aware work rather than one-off replies.
You give Hermes a real job, not just a prompt.
It works through connected systems, files, scripts, browser sessions, or other data sources.
It produces the draft, report, answer, checklist, or next step.
Useful preferences, context, and patterns can carry forward.
A repeatable procedure can become a reusable capability.
The assistant has a better starting point the next time similar work comes up.
The next run starts ahead.
Task
Tool use
Result
Memory
Skill
Better next run
Memory
Hermes Agent has a built-in memory system for compact, curated facts, searchable past conversations, and optional external memory provider plugins for deeper cross-session recall. The important distinction is that memory is not just chat history. It is the information the assistant should carry forward so future work starts with better context.
Hermes has built-in memory files called MEMORY.md and USER.md. MEMORY.md is for the agent’s notes about projects, environments, workflows, and lessons learned. USER.md is for user preferences, communication style, and other profile details. They are kept compact and loaded at session start, so key facts are ready when work begins without asking you to restate them.
A conversation can contain many details that are useful once but should not become permanent memory. Hermes preserves important facts separately from ordinary chat history, while still storing past conversations so the assistant can search them when a specific earlier discussion matters. That keeps curated memory focused without losing access to prior work.
For deeper memory, Hermes can use one optional external memory provider plugin at a time without replacing built-in memory. Several providers are available, including Honcho, each adding capabilities like semantic search, automatic memory extraction, session summaries, and richer cross-session user modeling.
Honcho is an optional external memory provider for deployments that need more than built-in memory and session search alone. It can build a longer-running model of the user, the AI assistant, and their work together. That makes it especially relevant for private assistants that should improve across email, reports, recurring workflows, and multiple communication channels.
Practical work
For a business owner, the useful examples are not abstract agent demos. They are reviewable drafts, reports, answers, searches, and follow-up lists prepared from real company records.
A message can be matched with account history, then turned into a draft for review.
Draft email
“A customer asked where the renewal terms landed. Check the demo account notes and draft a reply.”
Confirms the renewal date, cites the last note, and leaves the message ready for approval.
Information from active systems can become recurring summaries, exception reports, or status updates.
Weekly report
“Every Monday at 8 AM, summarize new sales leads and flag anything that needs follow-up.”
Groups new leads, stale opportunities, overdue replies, and suggested next actions.
Questions can be answered from company records such as files, docs, CRM notes, or internal data.
Sourced answer
“What did we promise this client in the last renewal conversation?”
Returns a concise answer with references to the demo proposal and CRM note.
Stale conversations, open loops, overdue replies, and next steps can be surfaced for review.
Follow-up list
“Review the last two weeks of demo inbox messages and list open follow-up items.”
Surfaces owners, dates, promised actions, and the next recommended draft.
Browser automation can help with websites, information gathering, and form-heavy tasks.
Browser task
“Open the demo vendor portal, find the current policy PDF, and summarize expiration details.”
Collects the visible details and prepares a review note before any meaningful action.
Repeated patterns can become candidates for a formal workflow or scheduled automation.
Saved workflow
“I noticed you ask for this report every Friday. Should I set up a recurring version?”
Offers to preserve the process as a reusable weekly lead follow-up report.
Architecture
Hermes Agent can be used from a command-line interface, but business deployments often depend on an always-on gateway process and a separate decision about where terminal work should execute.
The gateway process is the part of Hermes that lets the same assistant receive and respond through messaging platforms and other frontends. The terminal backend is the execution environment for shell commands, scripts, file operations, and other terminal-style work.
Docker can fit into either side of that picture. One setup keeps Hermes running on the host while terminal work runs in a Docker sandbox. Another runs the Hermes gateway itself in Docker, usually with persistent state mounted into the container. A more advanced setup can combine both ideas, but it needs deliberate handling of mounted files, credentials, network access, updates, and human approval rules.
Reach
The gateway is the long-running Hermes process that connects the assistant to messaging surfaces such as Telegram, Discord, Slack, WhatsApp, Google Chat, email, and other supported platforms.
Execution
The terminal backend determines where shell commands actually run: on the local machine, in Docker, over SSH, or in another supported sandboxed environment.
Isolation
In a host-installed setup, Hermes can use Docker as the terminal backend so terminal-style work runs inside a Docker sandbox instead of directly on the host.
Deployment
Hermes itself can also run in Docker as a persistent gateway, with its data directory mounted into the container and optional services such as the dashboard supervised alongside it.
Privacy
Hermes Agent can be deployed in a private environment, but privacy is not just a feature toggle. It depends on how the agent is installed, which model providers are used, which integrations are connected, what permissions are granted, where memory is stored, and how access is controlled.
An AI assistant connected to email, files, CRM records, or databases should not be treated like a casual chatbot. It should be configured with clear access boundaries, reliable source data, human review where appropriate, and a deployment model that matches the sensitivity of the work involved.
Where does the agent run?
Which model provider is used?
What data can it access?
Who can message it?
What actions require approval?
Are terminal tasks sandboxed?
How is memory stored?
Who maintains it?
Fit
Hermes is useful to different people for different reasons. Builders may want direct access to the framework. Business owners usually want the outcome.
Hermes is a strong fit for builders who are comfortable installing, configuring, extending, and self-hosting agent software.
Command-line tools
Self-hosting
API keys
Servers or cloud environments
Model providers
Tool configuration
Debugging integrations
The value is the working assistant, not becoming responsible for the deployment. A service like Norse Computer handles:
Initial setup and deployment
Permissions matched to your accounts
Workflows designed with you
Assistant instructions and skills built for the work
Real scenarios tested before launch
Ongoing maintenance and improvement
Norse Computer
Hermes Agent is the core technology. Norse Computer handles the implementation work around that core technology.
A raw Hermes installation is powerful, but a useful business assistant needs more than installation. Norse Computer deploys Hermes Agent in a reliable, secure, and maintainable way — so you get a working assistant without becoming a cloud infrastructure operator. That lowers long-term total cost of ownership for you.
Business owner or executive
Norse-configured assistant
Hermes Agent
Private environment, integrations, workflow scope, permissions, testing, support
Frequently asked questions
Hermes Agent is a better fit when the task depends on what is actually in your files, accounts, and systems today. A chatbot mostly responds from the prompt in front of it. Hermes can use a computer and browser to go look, run commands, open websites, and work through the steps needed to produce a real output. That matters when there is no ready-made integration, when the answer sits behind a login, or when useful work requires checking several places before anything is ready to review. The practical difference is follow-through: less back-and-forth explanation, more concrete preparation you can approve or use. A plain chatbot may be simpler for one-off questions or general conversation.
Yes. Hermes Agent is open source and MIT-licensed, which means the code can be inspected, modified, and deployed by technical users subject to the license terms. That openness is useful for self-hosting and customization, but it does not remove the practical work of deployment, configuration, security review, workflow design, and maintenance.
Hermes can connect to business software and integrations, but the exact connections depend on setup, permissions, available integrations, and custom configuration. Some workflows may work through existing APIs or connectors. Others may require browser-based work, file access, custom scripts, or a narrower first version that produces drafts and summaries before deeper integration is added.
It can be configured to work with email. In practice, that should be scoped to the accounts, labels, inboxes, or workflows that actually matter for the assistant. For sensitive communication, the safer pattern is usually review-first: the assistant researches context, summarizes threads, or drafts replies, while a person reviews meaningful messages before anything is sent.
Hermes Agent remembers useful context across sessions, but it does not treat every message as permanent memory. It has built-in memory for compact, curated facts, and it can be configured with external memory providers for deeper recall. It can also search past conversations when a specific earlier discussion matters. A good deployment decides what should be remembered, where it is stored, and what should stay temporary.
Yes. Docker can be used in two different ways. Hermes itself can run in a Docker container, including as a persistent gateway process. Separately, Docker can be used as the terminal backend, which means Hermes may run on the host while terminal commands execute in a Docker sandbox. A production setup can use either pattern or combine them, but mounts, credentials, network access, update process, and human approval rules still need careful configuration.
It can be configured for private and controlled use, but safety is not automatic. It depends on where the agent runs, which model providers are used, what data it can access, how memory is stored, whether browser and terminal work are sandboxed, and which actions require human review. The important point is to design the assistant around the sensitivity of the data and the consequences of each workflow.
Hermes Agent is best suited to work that is digital, repeated, and reviewable. It is strongest when it can pull context from the systems you already use, do the preparatory work, and leave a person with something concrete to review, refine, or approve. Because it can write code, it can also be a strong fit for building apps, especially internal tools and dashboards. It is less suited to work that depends on relationship judgment, nuanced prioritization, or irreversible decisions. The right starting point is usually the workflows you already repeat and can describe clearly.
In some cases, yes, an AI assistant with the right configuration can take on much of the digital work an executive assistant does: research, summaries, drafts, follow-up lists, reports, and recurring checks. For roles built around that kind of repeatable, reviewable work, it can replace a human hire. In other cases, a person still adds value — relationship management, sensitive communication, nuanced prioritization, and judgment on consequential decisions. The practical question is which parts of the role are digital enough to automate and which still need a person in the loop.
Further reading
These links point to the project and documentation maintained by Nous Research. They are useful if you want to inspect the underlying technology directly.
Hermes Agent is powerful, but the real value comes from configuring it around the work you actually need to delegate. Norse Computer deploys Hermes Agent as a private AI executive assistant connected to your day-to-day software, priority workflows, and business context.