Problem or Use Case

When configuring webhook routes in config.yaml, there is no way to specify which model or provider should be used for a given route's agent run. All webhook-triggered runs inherit the global model/provider configuration.

This is limiting when different webhook events have different complexity requirements. For example, a GitHub PR code review route benefits from a high-capability model, while a simple deploy notification route could use a smaller, faster, cheaper model. Today, the only workaround is running multiple Hermes instances with separate HERMES_HOME directories, each configured with a different model and listening on a different port.

Proposed Solution

Add optional model and/or provider fields to the webhook route configuration schema:

platforms:
  webhook:
    enabled: true
    extra:
      routes:
        github-pr:
          events: ["pull_request"]
          secret: "github-webhook-secret"
          model: "anthropic:claude-sonnet-4-20250514"
          prompt: |
            Review this pull request:
            Repository: {repository.full_name}
            PR #{number}: {pull_request.title}
          skills: ["github-code-review"]
          deliver: "github_comment"
          deliver_extra:
            repo: "{repository.full_name}"
            pr_number: "{number}"

        deploy-notify:
          events: ["push"]
          secret: "deploy-secret"
          model: "ollama:llama3"
          prompt: "New push to {repository.full_name} branch {ref}: {head_commit.message}"
          deliver: "telegram"

The model field would accept the existing provider:model syntax. When omitted, behavior remains unchanged (falls back to the global default).

Additional Context

The skills field already allows per-route customization of agent capabilities. A model field would be a natural extension of this pattern, giving route authors full control over the cost/capability tradeoff per event type.

Alternatives Considered

No response

Feature Type

Gateway / messaging improvement

Scope

None

Contribution

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

Debug Report (optional)