Hermes Agent Workflows for Malaysian SMEs: September 2026 Update

What Is New in Hermes Agent?

As checked on 19 September 2026, the latest stable release listed by Nous Research is Hermes Agent v0.21.3, released on 14 September. Its highlighted changes address remote Desktop and Cloud sign-in reliability and duplicate database writer handles in long-running processes. These are operational fixes that matter when a team depends on an agent throughout the working day. See the official September release notes.

For Malaysian SMEs, the more useful question is what a dependable agent should do each day. Below are three proposed workflow designs using capabilities described in the current documentation. They are not customer case studies, measured savings, or claims that all the features arrived in this patch. Test the capabilities available in your installed version before rollout.

The Building Blocks: Skills, Schedules, and Connected Tools

Hermes supports reusable skills that package a task procedure and supporting material. Its official skills documentation also describes automation blueprints: a skill can carry a proposed schedule and delivery settings, which the user reviews before scheduling. A saved skill gives the team a procedure it can inspect and revise; it is not proof that every future run will be correct.

The scheduled-task documentation covers one-off and recurring jobs, attached skills, and delivery to configured chats or local files. It also supports script-only jobs without an LLM call. Keep fixed calculations and simple data checks in code; use a model where interpretation or a written summary is useful. Connections, credentials, and the scheduler service must be configured and tested for unattended work.

Workflow 1: A Daily Operations Brief

Start with an approved export of open service requests, orders, or project tasks. A scheduled job reads the records, groups items by owner and due date, and prepares a short internal brief. The output should link back to the source records, show when the data was collected, and separate overdue items from records that are missing information.

• Input: a read-only export or supported API connection with only the fields needed for the brief.
• Processing: calculate counts and overdue dates in code; let the model summarise the checked results.
• Delivery: send the brief to one authorised internal destination and record whether delivery succeeded.
• Review: the operations owner checks exceptions and decides what happens next; the agent does not promise dates to customers.

Workflow 2: Reminders for Pending Approvals

A procurement or budget team could use an agent to summarise requests waiting for approval. The existing business system remains responsible for approval status, spending limits, and who is authorised to decide. Hermes would read that status through a scoped integration, prepare a reminder, and route it to the responsible person.

• Check the current approval state before preparing a reminder so completed requests are not chased again.
• Track reminder history to avoid duplicate messages when a job retries.
• Keep supplier commitments, purchase-order release, budget approval, and payments in the authorised business workflow.

This is an integration design, not an out-of-the-box procurement feature or a claim that GreatRise has deployed Hermes for a customer. When the underlying approval process is still spread across spreadsheets and email, define that process first through business process automation.

Workflow 3: A Weekly Report with Source Checks

A reporting job could collect approved data exports, calculate totals and changes, and draft a management summary. Each figure should remain traceable to a source file or record. If an export is missing or older than the agreed reporting window, the report should state that gap instead of presenting a complete-looking result.

• Agree the reporting period, timezone, included records, and calculation rules before scheduling the job.
• Use code or the reporting system for totals; use the model to explain verified results without inventing causes.
• Have the report owner review the draft before it reaches management or clients.

What to Check Before Updating an Existing Installation

Record the installed version, model provider, enabled tools, and jobs your team relies on. Keep a backup and a recovery path appropriate to your deployment. After applying an update, test sign-in, a representative task, a scheduled run, and delivery to the intended destination. A successful chat reply alone does not establish that overnight work will run correctly.

Review permissions at the same time. The Hermes security documentation describes user authorisation, command approval, and isolation controls. Business approvals still need to be enforced by the connected application and account permissions. Self-hosting the runtime does not mean that cloud model calls or messaging integrations keep all data inside your network.

Measure One Workflow Before Expanding

Choose one recurring task with a named owner, known source data, and a result that can be checked. During the pilot, record completion failures, corrections, review time, duplicate deliveries, and total running cost. Include hosting, model usage, integration maintenance, and staff oversight. Compare the reviewed output with the current process before deciding whether the change is worthwhile.

GreatRise helps Malaysian businesses scope AI workflow automation around their actual systems and approval rules. For a single agent with a defined job, see AI agent development in Malaysia. The implementation should start from the work your team needs done, then select the agent runtime and integrations that fit it.