mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-25 17:18:11 +00:00
The multiplex cron path only used use_cron_store() to scope storage paths (jobs.json, heartbeat files), but _get_lock_paths() and the agent execution path in cron/scheduler.py resolve via _get_hermes_home() → get_hermes_home() which checks _HERMES_HOME_OVERRIDE, a separate ContextVar. Without set_hermes_home_override(), the .tick.lock, config.yaml, .env, and secrets all resolved to the default profile instead of the per-profile home. This matches the web_server.py pattern (line 11994) which sets both set_hermes_home_override(home) AND use_cron_store(home), and the _profile_runtime_scope pattern used for the multiplexed inbound path. Found via 3-agent parallel review of salvaged PR #69529. |
||
|---|---|---|
| .. | ||
| scripts | ||
| __init__.py | ||
| blueprint_catalog.py | ||
| executions.py | ||
| jobs.py | ||
| lifecycle_guard.py | ||
| scheduler.py | ||
| scheduler_provider.py | ||
| suggestion_catalog.py | ||
| suggestions.py | ||