# Copy the relevant keys into ~/.hermes/config.yaml on the host/WSL2 side.
# Qwen is published by Compose only on host loopback.
model:
  provider: openai-api
  default: qwen3.8-27b
  base_url: http://127.0.0.1:8103/v1

# The API server receives requests from the local OMNI conductor. Hermes picks
# its API-server toolset for this platform.  The dynamic MCP toolset below is
# the only path from a run-bound OMNI ticket to screen, computer, files and
# webcam actions on the paired Windows node.
toolsets:
  - hermes-cli
  - mcp-omni_windows
  - mcp-nelloz_models

# Official Hermes MCP stdio configuration.  OMNI_ROOT must be the absolute
# path of this outputs/OMNI folder as seen by the process that runs Hermes.
# The bridge itself is loopback-only and every tool call additionally requires
# the run ticket injected by the authenticated node gateway.
mcp_servers:
  omni_windows:
    command: python
    args:
      - -m
      - desktop.windows.hermes_mcp
    env:
      PYTHONPATH: "${OMNI_ROOT}"
      OMNI_HERMES_BRIDGE_URL: "http://127.0.0.1:8766/v1/hermes/node-actions"
      OMNI_HERMES_BRIDGE_TOKEN: "${OMNI_HERMES_BRIDGE_TOKEN}"
    timeout: 120
    connect_timeout: 15
    supports_parallel_tool_calls: false
  nelloz_models:
    command: python
    args:
      - -m
      - orchestrator.model_tools_mcp
    env:
      PYTHONPATH: "${OMNI_ROOT}"
      OMNI_CONDUCTOR_URL: "http://127.0.0.1:8100"
      OMNI_CONDUCTOR_TOKEN: "${OMNI_CONDUCTOR_TOKEN}"
    timeout: 1800
    connect_timeout: 15
    supports_parallel_tool_calls: true