NousResearch/hermes-agent

Choose this fork if you want a more customized, Windows-friendly Hermes Agent and can tolerate being far from upstream. Stick with upstream if you need the widest integration coverage, faster access to recent fixes, or lower maintenance risk.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

Choose this fork only if you want its custom model/default/runtime changes and are comfortable trading away upstream breadth and update velocity. For most adopters who need full Hermes Agent coverage across messaging, docs, and platform integrations, upstream is the safer choice.

Choose this fork if RabbitSync support is the reason you are adopting Hermes Agent. Choose upstream if you want the broadest set of current fixes, integrations, and ongoing maintenance.

Prefer this fork only if you specifically want a frozen upstream snapshot. For most adopters, upstream is the better choice because this fork adds nothing visible and is already behind active fixes and features.

Prefer upstream unless you specifically need this exact snapshot. For most adopters, the fork offers no added capability and is materially behind current upstream work.