Subshell Docs

Hermes Agent

Run Hermes Agent as a Subshell agent.

Before you start

Install hermes using the vendor instructions and authenticate it under the execution account. Ask an administrator to enable the harness under Settings → Server Settings → Plugins in the server dashboard's sidebar. Follow Install an agent CLI to confirm detection on the target node.

Launch

  1. In the server dashboard's sidebar, choose Subshells, select New subshell, and choose Hermes Agent.
  2. Select a preset or configure the supported launch settings.
  3. Choose the target node and an existing project directory.
  4. Launch and confirm that the CLI opens normally.

The plugin detects hermes through PATH and its known locations. HERMES_PATH can identify the binary explicitly in the execution environment. Before changing that override, see Files and paths for configuration locations and service-environment guidance.

MCP and session behavior

Hermes uses one-time MCP registration on each execution host. Follow MCP configuration to locate the registration command in the preset form and run it on the execution host before using cross-agent tools. The built-in plugin declares MCP and settings capabilities; it doesn't declare automatic conversation resumption or attention hooks.

Subshell runs the real CLI rather than proxying its provider API. Provider configuration, usage limits, and CLI-specific permissions remain the agent's own settings.

Register MCP

When the node binary is on PATH, the portable registration is:

hermes mcp add subshell --command subshell --args mcp

Use the host-specific command shown by Subshell if its binary has a different name or path.

Next steps

Read MCP configuration, Presets, and Agent and launch errors.

Edit on GitHub

Last updated on

On this page