Hermes Agent and Hubzoid both support memory, reusable skills and scheduled work. The useful distinction is how those capabilities are shared.
Hermes Agent (opens in a new tab), from Nous Research, works from your terminal and messaging apps, retaining preferences and developing procedures as you use it.
Hubzoid starts with a shared Hub. The team maintains its knowledge, instructions and tools in one place, then uses that foundation through chat, workflows and supported assistants.
Start with what you want to maintain: an assistant's working habits or a foundation teammates use under their own accounts.
At a glance
- Choose Hermes when you want an assistant that remembers your preferences and develops reusable ways to do your work.
- Choose Hubzoid when teammates need maintained shared context and different permissions to use the same internal tools.
- Both overlap. Hubzoid also saves corrections, runs reports for individuals and creates personal schedules from chat. Hermes also supports separate profiles and sharing procedures.
One task, built two ways
Imagine an operations lead needs a stock report before the Monday meeting.
In Hermes, they connect the stock data, explain what needs attention and refine the result. The procedure can become a reusable skill, with a scheduled task (opens in a new tab) delivering the report to their chat.
In Hubzoid, the operations lead builds the shared foundation:
- They record the reporting period, stock definitions and exceptions in the Hub.
- They use a coding assistant to build and check the stock lookup tool and report.
- An administrator grants teammates the tools and reports they need.
A teammate can ask for an enabled report in chat and run it as themselves. With scheduling permission, they can ask for it every Monday and confirm the schedule. My workspace holds their results and schedules. A live report link can keep opening the newest copy.
When the definition of available stock changes, the team updates one shared note for future work.
What Hubzoid gives a team
- A place for agreed knowledge. The Hub holds shared rules and procedures. Each conversation keeps its own history.
- Access for named people. Restricted tools are checked in code before execution. Personal runs use the requesting person's grants and connections.
- Personal and team reports. Schedules and live reports give teammates their own results and administrators an operating view. Code workflows can recover completed steps after a restart.
- Your own assistant and server. Supported MCP clients can use the Hub with their own model. Hubzoid, including its team controls, is Apache 2.0 open source (opens in a new tab).
Side by side
| Question | Hermes Agent | Hubzoid |
|---|---|---|
| Where does the work start? | An assistant with its own tools, memory and skills | A shared Hub of instructions, knowledge, skills and tools |
| What carries into later work? | Profile memory and reusable procedures | Authored Hub knowledge and explicitly saved learnings |
| How do you separate setups? | Profiles with their own settings, memory and credentials | Separate Hubs, accounts and capability grants |
| Can people schedule their own work? | Yes, with scheduled tasks and configured destinations | Yes, with personal schedules from chat and My workspace |
| What does MCP add? | Connections to external tools | Shared context and authorized tools for supported assistants |
Hermes has separate profiles (opens in a new tab), but its security policy (opens in a new tab) treats authorized callers within one shared adapter as equally trusted. Hubzoid checks restricted tools for each caller. Its ordinary Hub knowledge is still shared, so private records belong behind an appropriate access boundary.
How memory and skills work
Hermes combines persistent memory (opens in a new tab) with an agent-managed skills system (opens in a new tab). It can turn a successful procedure into a skill and revise it later. Optional approval controls let people review memory and skill changes.
Hubzoid's learned knowledge is explicit: a person with permission asks it to save a correction for later use across the Hub. Both retain useful learning, with different choices about who changes it and who receives it.
Can they work together?
Potentially. Hermes supports remote MCP connections and OAuth sign-in (opens in a new tab). It could be the assistant a person uses to reach a Hubzoid Hub.
That pairing has not been verified end to end. Test sign-in, context delivery, permitted and denied tools, and token renewal. Each person's assistant should connect as that person. A shared bot using one connection would act as the account that signed in.
Try both on one small task
Use the same stock data and expected report. Then check:
- What does the agent retain after you correct an answer?
- Can a colleague use the procedure without your personal credentials?
- Can different people reach only the tools they need?
- Who notices when the scheduled report fails?
Next step: try the Hubzoid quickstart and Hermes Agent (opens in a new tab) on one report your team already understands.