Skip to main content
Use RunInfra as a named custom provider in Hermes. Support level: ready. Connect supports automatic setup.
Connect writes the named provider in config.yaml and uses .env for literal keys. The recorded round trip used WSL. Native Windows paths still need confirmation.

​
Connect Hermes

Have Hermes installed, a workspace API key, and available RunInfra credits. Choose a catalog model with at least 64,000 context tokens. Connect requires that minimum for this setup.
The bare agent command is an alias for on. In an interactive terminal, Connect starts login if needed. Review and approve the proposed changes. Connect saves a snapshot, writes the provider and key settings, and makes a real Chat Completions request that uses credits. To choose a model during setup:
See Connect for status, diagnostics, and key replacement.

​
What Connect writes

When HERMES_HOME is set, Connect uses config.yaml and .env inside that directory. Confirm the active directory and profile. The native Windows targets above describe Connect’s file choices, not a confirmed native Windows installation. Connect writes these named-provider settings: Connect removes api_key and key_cmd from the RunInfra provider settings. It also removes the selected model’s api_key, key_env, key_cmd, and base_url fields so the named provider supplies them.

​
Key placement

Literal mode adds the RUNINFRA_API_KEY assignment to .env. The YAML references that variable through providers.runinfra.key_env; it does not store the literal key there. For helper mode:
Helper mode uses the launch environment instead of writing a new literal assignment. Connect keeps an existing .env assignment when another provider still uses that variable. Review the warning and check helper credential precedence separately.
Export RUNINFRA_API_KEY with your RunInfra API key in the environment that launches the app. Restart GUI apps and background services with that environment.On Windows, set RUNINFRA_API_KEY in your user environment, then fully restart the app. GUI and Start menu launches do not receive a terminal-only $env:RUNINFRA_API_KEY value. This launch guidance does not confirm native Windows path behavior.

​
Verify

Hermes v0.21.1 on WSL completed a verified round trip on September 8, 2026, using the Connect-written named provider and .env key. The request returned RUNINFRA_OK and was confirmed in RunInfra usage. Inspect the selected model and custom:runinfra provider:
This checks selection, not a reply or its destination. In an authorized isolated environment, run the follow-up command. Connect prints it but does not execute it:
The no-tools prompt is not a permission boundary. Confirm the reply and request destination separately.

​
Restart

Restart Hermes after editing files. Run hermes config get model to inspect selection. This does not verify a reply or its destination.

​
Known behaviours

Still check native Windows paths, HERMES_HOME and profiles, Hermes’s minimum context size, helper credential precedence, and restoration after Hermes saves changes. Connect’s 64,000-token minimum is a setup guard, not confirmation of every model’s behavior in Hermes. If Connect cannot safely read the YAML, environment assignments, or another provider’s credential references, it refuses the changes. Review both files before retrying.

​
Troubleshooting

​
Revert

In the recorded run, off restored config.yaml byte for byte and removed the added RunInfra key line from .env. With intact state and snapshots, off restores the original managed files from before the first on in the active connection. It removes files that did not exist then. Later on calls and key rotations keep that restore point. If Hermes or another editor changed a managed file, Connect refuses to overwrite it. Back up and review the edits before choosing to discard them:
Connect saves the current contents in a recovery snapshot and prints its id before restoring the origin. Keep the snapshots. If the origin snapshot is missing, cleanup does not guarantee original-byte restoration. See Connect recovery. Restore manual environment and profile changes yourself. File restoration does not restore external credentials or other profiles.

Connect

Set up, inspect, and restore your coding agent.

Chat completions

Read the request contract.

Models

Find model ids and context windows.