Skip to content

fix: report cronjob tool as available in hermes doctor#1180

Merged
teknium1 merged 1 commit into
mainfrom
hermes/hermes-447d1ebd
Mar 13, 2026
Merged

fix: report cronjob tool as available in hermes doctor#1180
teknium1 merged 1 commit into
mainfrom
hermes/hermes-447d1ebd

Conversation

@teknium1

Copy link
Copy Markdown
Contributor

Summary

Cherry-picked from PR #895 by @stablegenius49, rebased onto current main with conflict resolution (PR was 233 commits behind).

Sets HERMES_INTERACTIVE=1 via setdefault in run_doctor() so CLI-gated tool checks (like cronjob management) see the same context as the interactive CLI.

Why this works

The cronjob tool's check_fn requires one of HERMES_INTERACTIVE, HERMES_GATEWAY_SESSION, or HERMES_EXEC_ASK to report as available. Since hermes doctor runs from the CLI (same context as hermes), setting HERMES_INTERACTIVE is correct. Using setdefault ensures we don't override if already set.

Testing

  • Doctor tests: 8/8 passed (7 existing + 1 new regression test)

Fixes #878

Co-authored-by: stablegenius49 stablegenius49@users.noreply.github.com

Set HERMES_INTERACTIVE=1 when running hermes doctor so CLI-gated
tool checks (like cronjob management) see the same context as the
interactive CLI. Uses setdefault to avoid overriding existing values.

Cherry-picked from PR #895 by stablegenius49, rebased onto current
main with conflict resolution.

Fixes #878

Co-authored-by: stablegenius49 <stablegenius49@users.noreply.github.com>
@teknium1 teknium1 merged commit d425901 into main Mar 13, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: hermes doctor always reports the cronjob tool as "(system dependency not met)"

2 participants