Bug Description

The hermes doctor command always reports the cronjob tool as "(system dependency not met)", which is pointless.

Steps to Reproduce

1. Run hermes doctor

Expected Behavior

Not see "(system dependency not met)" for the cronjob tool.

Actual Behavior

Always see "(system dependency not met)" for the cronjob tool.

Affected Component

Other

Messaging Platform (if gateway-related)

N/A (CLI only)

Operating System

Ubuntu 24.04

Python Version

3.11.11

Hermes Version

vv1.0.0

Relevant Logs / Traceback

◆ Tool Availability
  ✓ terminal
  ✓ vision
  ✓ moa
  ✓ skills
  ✓ browser
  ✓ file
  ✓ tts
  ✓ todo
  ✓ clarify
  ✓ code_execution
  ✓ delegation
  ✓ memory
  ✓ session_search
  ✓ messaging
  ⚠ web (missing FIRECRAWL_API_KEY)
  ⚠ image_gen (missing FAL_KEY)
  ⚠ cronjob (system dependency not met)
  ⚠ rl (missing TINKER_API_KEY, WANDB_API_KEY)
  ⚠ honcho (system dependency not met)
  ⚠ homeassistant (system dependency not met)

Root Cause Analysis (optional)

The check for cronjob relies on the check for one of 3 environment variables being set. (IMHO, the way the check is done is weird in and of itself.)
None of those environment variables are set in the code pathway of the hermes doctor command leading up to the actual check.

I suspect there are other checks that are done in the same fashion and that persistently result in "(system dependency not met)" in the output of the hermes doctor command.

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

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