Skip to main content

​
Runtime Settings

Path: Headmaster’s Library → Runtime (PIN-protected) These settings configure the Hermes runtime engine — the background service that runs your agents. The runtime handles model inference, tool execution, memory storage, scheduled tasks, and MCP server connections.

​
Connection mode

The runtime runs on the same machine as the desktop app. No network configuration needed.What you see:
  • Status — Connected, Reconnecting, or Disconnected.
  • Port — the local port the runtime is listening on.
  • PID — the process ID of the runtime.
  • Uptime — how long the runtime has been running.
  • Version — the runtime version number.

​
Restart

Click Restart to tear down the current runtime process and start a fresh one.
Restarting does not lose your data — sessions and memory live in the user data folder, not in the process. Use restart when:
  • The runtime is stuck or unresponsive.
  • You changed the config file manually and need to reload it.
  • After installing a new skill or integration that requires a runtime restart.

​
Sessions

Click Sessions to see the list of active sessions on the runtime. Each session shows: You can delete a stale session from this list. This clears the runtime’s in-memory state for that session but does not delete the transcript file.

​
Schema-driven settings

The runtime exposes a configuration schema at /api/config/schema. The Settings UI reads this schema and renders the appropriate controls — text fields, dropdowns, toggles, sliders — with descriptions, defaults, and validation. This means when the runtime adds a new configuration option, the Settings UI picks it up automatically. You don’t need a desktop app update to see new runtime settings.

The Local Runtime

How the runtime works, where data lives, and log files.

Troubleshooting

Fixes for runtime not connecting, crash loops, and 401 errors.