Hermes Agent MT

What Hermes Agent MT does

Hermes Agent MT is a patched copy of the upstream Hermes Agent aimed at multi-tenant deployments. According to its fork notice, the changes add per-context memory isolation, group policy enforcement and integration with Swarm Map, a separate project from the same organization. The rest of the README is the upstream Hermes Agent documentation, covering the terminal interface, the messaging gateway, skills, cron scheduling and the six terminal backends.

Builds are published by CI as a container image at ghcr.io/cyborg-garden/hermes-agent-mt:latest. The organization was renamed from NimbleCoOrg to cyborg-garden and the image path changed with it. Git remotes redirect after a rename, but GHCR does not, so the old nimblecoorg path no longer pulls, while the older nimblecoai image path still pulls but is frozen at its last build on 2026-08-06. Anyone pinned to either path needs to repoint.

Key features

• Per-context memory isolation for multi-tenant use
• Group policy enforcement
• Swarm Map integration
• Container image published by CI to ghcr.io/cyborg-garden/hermes-agent-mt
• Upstream feature set documented in the README, including the TUI, messaging gateway, cron scheduler and six terminal backends

When to use it

• Hosting one shared agent where each chat context needs separate memory
• Running Hermes Agent for several users or groups from a single deployment
• Connecting a Hermes deployment to Swarm Map

Who it is for: Operators who run a shared Hermes Agent for multiple users or groups and need memory kept separate per context.

How it fits with Hermes Agent

It is a fork of Hermes Agent itself, tracking upstream NousResearch/hermes-agent with multi-tenant patches.

Note: After an organization rename the container image moved to ghcr.io/cyborg-garden/hermes-agent-mt, so the old nimblecoorg path no longer pulls and the nimblecoai path is frozen at its 2026-08-06 build.

FAQ