hermes - 💡(How to fix) Fix [Feature]: Support offline/air-gapped installation and local LLM configuration [1 participants]

Problem or Use Case

Hermes Agent cannot be deployed in offline or air‑gapped environments.

The current installation process requires downloading scripts, source code, and dependencies from external services (e.g. GitHub and public package registries). In environments without outbound network access, installation cannot be completed at all.

This makes it impossible to deploy Hermes Agent in enterprise, secure, or air‑gapped environments where offline installation is a hard requirement.

Proposed Solution

Provide an officially supported offline installation mechanism.

This could include:

Publishing a downloadable offline installation package (e.g. .tar.gz or .zip) containing: Source code Installation scripts Dependency manifests Documenting a step‑by‑step manual installation process that does not rely on curl | bash Ensuring the installation workflow works without any external network access The goal is to allow Hermes Agent to be installed entirely from local files in an offline environment.

Alternatives Considered

Manually modifying install scripts or copying files between machines

→ Fragile, error‑prone, and not reproducible.

Temporarily enabling external network access

→ Often prohibited by security policies and not acceptable in secure environments.

The proposed solution is better because it provides a clear, repeatable, and officially supported way to deploy Hermes Agent in offline or air‑gapped environments.

Feature Type

Configuration option

Scope

None

Contribution

• I'd like to implement this myself and submit a PR

Debug Report (optional)