Mesh Helm Get early accessEarly access

Mesh Helm and Hermes Desktop, side by side.

Hermes Desktop is the free desktop app for Hermes Agent, by Nous Research. Mesh Helm is a separate app that works beside it. This page says plainly what each one does.

The short answer.

Hermes Desktop is the free app to build with: chat, projects, and its own screens to set up models and channels.

The Mesh Helm app now does most of the same daily work: chat, scheduled jobs with every option, skills and MCP servers from the catalog, a task board, Git and logs. It uses the commands of Hermes for this, so Hermes does the work.

Add Mesh Helm when your agents run without you. It checks what each run delivered, asks before the same thing goes out twice, and puts everything that needs you in one list.

Both read the same Hermes folder on your Mac. You can use both at the same time.

Mesh Helm can also run without Hermes, on Mesh, the engine inside Mesh Bot. This page compares the two apps on Hermes.

What Mesh Helm adds.

AreaHermes Desktop (free)Mesh Helm adds
Scheduled jobsCreate, edit, run history, failure alerts.A check on each result. It flags a run that ends “ok” with almost no output. A result rule and a score from 0 to 100 for each job. A job form that sets the rule and the budget with the job.
Outside actionsApproval modes and allow lists.A question before an exact repeat of a send, post or create, from any profile.
What needs youLists for each feature and each profile.One ranked list across profiles, with the likely cause and the safe steps.
CostUsage by day and by model.Cost by profile and by automation, a month forecast, what one useful run costs, budgets that tell you at 80 % and over. A job budget that can stop the run and pause the job.
SafetySettings for each profile.One page for each profile: what it can do outside, the names of its keys, six kinds of risk with their fix. A risk grade and a test for each MCP server.
ProfilesMake, export, import.A copy that warns you when the source has a critical or high security point. A compare of two profiles, line by line. A delete that makes an export first.
ChangesA warning on a risky model switch.A list of the automations a change reaches, before you save, and a test run after. A trial run of a job with no send, on other models too. Versions of the setup of each profile, with what changed and when.
Runaway workThe engine can pause all new work with one command.A brake inside the engine that stops one profile in a loop, with the app closed. It is off until you turn it on. A line before a run that will probably fail.
MCP serversAdd and test a server. The engine has a tool picker in Terminal.Each tool with what it can do, its use and its last error. An alert when the text of a tool changes after you accepted it.
Finished runsThe run history of each job.A receipt of facts for each run, to accept or send back. A count of what the checks caught in 30 days, and a report as text.
Engine updatesThe update itself.A check after each update that pauses only what broke, and a count of the jobs that still pass.
ErrorsGrouped for each job.Grouped across jobs, tools and channels.
Time awayA recap when you open a session again.What happened across all profiles since you left, in five lines or fewer. Alerts to a channel with the app closed.
Claude CodeImports sessions.Also brings skills, MCP servers and deny rules, item by item, with keys left out, and a brief.

The same work, in the Mesh Helm app.

These are in the app, not in the pages inside Hermes Desktop. Each one calls a command of Hermes.

  • Scheduled jobs: every option of a job, such as skills, a script, a time zone and a repeat count. The form has lists for the time, the model and the target. You can also set up or change a job in a chat.
  • Skills: search the catalog, see a preview, install and update. Hermes scans a skill first. The app does not install a skill that the scan blocks.
  • MCP servers: the catalog, add, remove and test, with a risk grade after the install.
  • A task board: make a task, give it to a profile, comment, block, close. A task that ran shows its cost and the check of its steps.
  • Git for the folder of a chat: see the changes, stage, commit, push and open the pull request page.
  • Chat: a timeline of your messages, export to a web page or to text, a second window to see two chats, and a message that waits for the end of the run.
  • Logs of Hermes, also for one session. A search in the memory of all profiles. Light and dark, and four colours.
  • Two chats side by side in one window. A chat in its own worktree. A message that steers a run in progress.
  • A Git review: the history, the branches, and all changes against the main branch.
  • The task board with links between tasks, and more than one board.
  • A check that tells you, after a Hermes update, which command the app can no longer use.
  • Trial run, Review, Changes, MCP tool control, Context X-ray and the Night Brake settings.
  • A copy of Mesh Helm’s own data each day, a restore, and an export of all of it as one file.

What Mesh Helm does not do today.

  • It has its own setup for four model providers and for Telegram, Discord and Slack. You type a key or a token in a Terminal window, so the app never sees it. For all other kinds, it opens the setup of Hermes in a Terminal window. An MCP server from the catalog installs in the same way.
  • The budget stop works only while the app is open. It stops scheduled jobs and the chats in the app. It does not stop a chat in another program.
  • The Duplicate Guard sees only actions that go through Hermes tools. It matches exact repeats. The check for a message that is almost the same is a switch in the app, and it is off at the start.
  • A trial run does not hold terminal and file tools. It is close to a scheduled run, not the same: Hermes adds its own text to a scheduled run.
  • The Night Brake stops the tools of a profile. A model call that is in progress ends first.
  • “What a tool can do” in MCP tool control is a hint from the name of the tool and from what the server says. It is not a proof.
  • There is no Windows or Linux version.

When you do not need Mesh Helm.

You run one profile. You have no scheduled jobs. Your agents send nothing outside. Then Hermes Desktop is all you need.

How the two fit together.

Hermes Agent is the engine. It runs your agents and keeps your sessions, profiles, skills and jobs in its own folder.

Mesh Helm adds a small plugin inside the engine. The plugin records facts about each step and asks before a repeat of an outside action. When you turn on the Night Brake or start a trial run, it also refuses tool calls. The Mesh Helm app reads those facts and shows them.

If you stop using Mesh Helm, everything in the Hermes folder stays and works as before.

Checked against Hermes Agent 0.23.1 in November 2026. Hermes Agent and Hermes Desktop are free and open source, by Nous Research. Mesh Helm is an independent product and is not affiliated with Nous Research.

Mesh Helm is not on sale yet. Leave your email address and you get one message when the Mac app is ready.

Get early access