Hermes vs Manus: How I'd Set Up Each Agent Step By Step, And Which Jobs Go Where

Hermes vs Manus comes down to who runs the machine: you install Hermes Agent on hardware you control, while Manus runs your tasks on its own cloud computers unless you point it at a folder on your desk.

I'd set up both before picking a winner, because the setup itself tells you which one suits your work.

Hermes Agent is open-source software from Nous Research, released under the MIT license, and it talks to almost any model provider.

Manus calls itself an autonomous general AI agent that works inside a sandbox with internet access, a persistent file system and the ability to install software.

Below are the steps I'd follow for each one, the settings I'd change first, and a verdict by job.

If you want my team to map your own jobs onto the right agent, book a free SEO strategy session.

The difference that decides everything else

Hermes is a program you own.

Its settings live in ~/.hermes/config.yaml, its commands run on a terminal backend you pick, and its brain is whichever model provider you connect.

Manus is a service you sign into.

By default each task gets a temporary cloud sandbox, and the Cloud Computer help article says that sandbox is eventually closed after the task, while your outputs stay in the chat history.

Manus has moved closer to your desk this year, because its desktop app, now called Manus Studio, can work inside a folder on your own computer.

Even then, the Manus Studio docs say the planning of every step happens in the Manus cloud and only the commands execute locally.

No official source compares the two products, so the comparison below is my own reading of each vendor's docs.

Hermes vs Manus side by side

The rows come from the Hermes configuration, messaging and provider pages and from the Manus connectors, Automations and Studio docs.

Step 1: install Hermes and pick a model

1. On Linux, macOS or WSL2, run curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash.
2. On native Windows, use the PowerShell one-liner from the installation page.
3. Run hermes model and choose a provider: Nous Portal, Anthropic, OpenAI, OpenRouter, Google Gemini, xAI, a local Ollama or LM Studio server, or a custom endpoint.
4. Run hermes and hand it a small job, such as listing the files in a folder, to check the tools respond.

The providers page runs to dozens of options, so start with one you already hold an account with.

If you only want local models, begin with Ollama or LM Studio and keep the first jobs small while you learn what your hardware can handle.

Step 2: put Hermes in your chat app behind an allowlist

Run hermes gateway setup and choose the platform your team already lives in.

The messaging gateway docs cover Telegram, Discord, Slack, WhatsApp, Signal, SMS, email, Microsoft Teams, LINE, Matrix and more, all handled by a single background process.

Next, run hermes gateway install so the gateway keeps running as a service after you log out.

Before you share the bot, fill in an allowlist such as TELEGRAM_ALLOWED_USERS, the way the team Telegram guide does it.

That one line is what separates a private assistant from a bot anyone could message.

Step 3: open Manus and choose where each task runs

Sign in on the web and run your first job in the default cloud sandbox, which needs nothing installed.

For work on local files, download Manus Studio for macOS (Apple Silicon) or Windows and sign in with the same account.

Switch on Work locally in the chat box, then click Choose a folder so the task gets its own workspace.

For anything that has to keep going while your laptop is shut, Manus points you to a Cloud Computer, a dedicated Ubuntu machine you subscribe to.

So a Manus task has three possible homes, and you choose one per job.

🔥 Want the Hermes config and Manus prompts I'd start a client on? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members comparing agent setups like these. → Join the AI Profit Boardroom

Step 4: set the permission mode before Manus touches a folder

Click Permissions in the Studio chat box and you get three modes.

• Ask for approval: every local action waits for you.
• Approve for me (the default): an automatic review lets safe actions through and blocks high-risk ones.
• Full access: local actions run with no approval at all.

I'd stay in Ask for approval for the first week and give each task the smallest folder it needs.

One detail people miss: the approval modes limit what Manus changes, not what it reads, so a command can still open other files your user account can open.

On Windows, both approval modes need a one-time click on Enable safe modes first.

Step 5: schedule the same job in both

In Hermes, ask in chat or use the CLI.

hermes cron create "0 18 * * 1-5" \
  "Read tomorrow's bookings in ~/jobs/bookings.csv, group them by area and list the parts each job mentions. Save the sheet to ~/jobs/sheets/. Draft only: do not message customers." \
  --name "Next-day job sheet" \
  --deliver telegram

The cron docs say a job can deliver to the chat it came from, to local files or to a configured platform, and a webhook route can fire a job the moment an outside event lands.

In Manus, open Automations, click Create and pick Schedule, Trigger or Advanced automation.

The Automations guide asks for an exact time with a timezone, and it recommends a Test run before you lean on a new automation.

Older Manus scheduled tasks keep running; they simply show up inside Automations as schedules now.

Step 6: connect your business apps

Manus gets you connected faster.

Its connector directory lists 416 connectors in three types, App, MCP and API key, with Gmail, Outlook, Google Calendar, GitHub, Shopify, Slack, Notion and HubSpot among them.

When a task needs a connector you haven't switched on, Manus suggests it in the chat and enables it only after you say yes.

Hermes plugs tools in through MCP servers listed under mcp_servers in config.yaml, or through plugins from its catalog, which the v0.23.0 release notes say grew past 1,050 entries.

For a server you don't fully trust, set trust: untrusted, and the MCP config reference says every write-capable call then needs your approval.

Manus accepts custom MCP servers by URL or by command too, so internal tools are reachable from either side.

📞 Not sure which jobs belong on your own box and which belong in Manus's cloud? Book a free SEO strategy session and my team will walk through your workflows with you. → Book your free strategy call

Approvals: what each tool actually asks you about

Hermes checks every shell command against a list of dangerous patterns, and approvals.mode sets the policy to smart (the default), manual or off.

Cron runs default to cron_mode: deny, so a scheduled job that hits a dangerous command gets blocked instead of waved through.

What Hermes doesn't ship is an approval step for outgoing messages, so I write "draft only" into every job that touches a customer.

In Manus, the documented approvals sit on local actions in Studio and on switching connectors on.

Its own automation examples route drafts to a review channel rather than straight to a customer, and I'd copy that habit.

The full rules are on the Hermes security page and in the Studio permission table.

Operator example: an electrician's next-day job sheet

Here's how a two-van electrical firm could run the same evening job on each tool.

On Hermes:

1. Hermes runs on the office mini PC with the local backend and Telegram connected.
2. At 6 pm on weekdays, the cron job above reads the bookings file in a shared folder.
3. It groups tomorrow's jobs by area, lists the parts each booking mentions, and saves a sheet.
4. It posts the sheet to the owner's Telegram chat so the morning briefing starts from it.

On Manus:

1. The owner turns on Work locally in Manus Studio and picks the bookings folder.
2. A Schedule automation fires at 6 pm on weekdays in the owner's timezone.
3. Manus builds the same grouped sheet and returns it in the task.
4. Because local Studio tasks need the computer on and Studio open, the office PC stays awake.

Both get the sheet out; Hermes keeps every byte on the office machine, while Manus asks for less setup.

Operator example: a small web agency's pull requests

1. In Manus, the agency adds a Triggered task on GitHub that fires when a non-draft pull request targets main.
2. Manus summarizes the change, points out risky files and checks whether tests cover the main behavior.
3. It leaves a review only when there's a clear problem, and otherwise sends the summary to the developer inside Manus.

In Hermes, the agency would point a GitHub webhook at its gateway so the review runs when a PR opens, as the PR review guide walks through.

That guide needs a publicly reachable URL for the Hermes instance and the gh CLI signed in on the gateway host, and it suggests running the gateway in a sandbox such as Docker when the endpoint faces the internet.

Manus reaches the same place with fewer moving parts, while Hermes keeps the review on the agency's own model and server.

Gotchas I'd plan around

• Manus Studio supports Apple Silicon Macs and Windows 10 and 11 only; Linux and Intel Macs are out.
• A Studio task sent from your phone only runs while the computer is on, awake and running Studio.
• Manus Flex, the bring-your-own-key mode, is still in beta, and its docs say the setup form has no custom endpoint field.
• Some Manus triggers are checked at intervals rather than instantly; GitHub, Shopify, Webhook and Mail Manus events arrive as they happen.
• Hermes needs a machine that stays on for the gateway and cron, whether that's a server, a mini PC or a cloud backend.
• Setting Hermes approvals to off removes every safety prompt, so save it for throwaway containers.

Verdict by job type

• Pick Hermes if you want to choose the model, keep files on your own hardware and talk to the agent in WhatsApp, Signal or Teams.
• Pick Manus if you want results today with nothing to install, a big connector catalog, and website and video tools built in.
• Pick Hermes for unattended jobs on a server you already run.
• Pick Manus for research across many items, where Wide Research gives each item its own agent.
• Run both if your team splits private back-office work from public-facing research and content.

For a cloud-to-cloud matchup, my Grok Bot vs Manus walkthrough sets Manus against another hosted agent.

The Hermes configs behind setups like these are inside the AI Profit Boardroom.

Also On Our Network

• 🌐 Five small-business use cases that show where Hermes or Manus fits better
• 🌐 The nine-row scorecard that rates Hermes and Manus out of 10
• 🌐 Five copy-paste prompts that give Hermes the back office and Manus the studio
• 🌐 Which AI models to run in Hermes or through Manus Flex, with GoldieBench scores
• 🌐 The complete Hermes vs Manus guide on the AI Profit Boardroom blog

FAQ: Hermes vs Manus

Do I need to install anything to use Manus?

No. Tasks run in a cloud sandbox from the web by default. You only install Manus Studio when you want Manus working on files on your own Mac or Windows PC.

Can Hermes run without any cloud model provider?

Yes. The providers page lists local Ollama, LM Studio and custom endpoints. You still need a machine that stays on for the gateway and cron jobs.

Which Manus Studio permission mode should I start with?

Ask for approval, with the smallest folder the task needs. Move to Approve for me once you trust the job, and keep Full access for tasks you fully trust.

Will Hermes ask before it sends a message for me?

Hermes approvals cover dangerous commands and write calls on untrusted MCP servers, not outgoing messages. Write "draft only" into any job that touches customers.

Does Manus run on Linux?

Manus Studio does not; it supports Apple Silicon Macs and Windows 10 and 11. The Cloud Computer itself is an Ubuntu Linux machine in the cloud.

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

About Julian

I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

• I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
• I've grown a YouTube channel to 400,000+ subscribers.
• I wrote "Link Building Mastery".
• My Udemy courses have taught over 29,000 students.

→ Get my best AI training inside the AI Profit Boardroom

Install Hermes on one spare machine, run one Manus task in the cloud, and book a free strategy session if you want my team to help split the work.

Set both up this week and let your own jobs settle Hermes vs Manus.