mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-29 18:46:59 +00:00
d464ae3652
Per-job cron inference pins are now user-owned: the agent-facing cronjob tool schema no longer exposes model/provider/base_url, and the registered handler ignores them even if a model hallucinates the old parameters. Users set pins via the dashboard, hermes cron create/edit --model/--provider, or jobs.json directly — and once set, a pin sticks until the user changes it. Existing agent-era pins are grandfathered untouched. New cron.model / cron.model_provider config keys give the cron fleet its own default model, independent of the chat model. Fire-time resolution: per-job pin > cron.model > HERMES_MODEL > model.default. An axis covered by the explicit cron-fleet default is deliberate routing, not drift, so the #44585 fail-closed guard skips it — switching your chat model with /model or hermes model no longer breaks unpinned cron fleets. - tools/cronjob_tools.py: drop model param from agent schema + handler; remove now-dead _resolve_model_override - cron/scheduler.py: cron.model/model_provider resolution + per-axis drift-guard skip - cron/jobs.py: snapshot resolution mirrors the new precedence - hermes_cli/subcommands/cron.py + hermes_cli/cron.py: --model/--provider on hermes cron create/edit - hermes_cli/config.py: cron.model / cron.model_provider defaults - docs: cron.md model-resolution tip rewritten |
||
|---|---|---|
| .. | ||
| scripts | ||
| __init__.py | ||
| blueprint_catalog.py | ||
| executions.py | ||
| jobs.py | ||
| lifecycle_guard.py | ||
| scheduler.py | ||
| scheduler_provider.py | ||
| suggestion_catalog.py | ||
| suggestions.py | ||