hermes - 💡(How to fix) Fix image_gen and vision tools not working after fresh install

Problem Description

After installing Hermes Agent, image_gen (image generation) and vision (image recognition) don't work out of the box — users have to debug deep into the code to get them running.

Issue 1: image_gen toolset not enabled

Symptom: MiniMax image generation plugin exists at plugins/image_gen/minimax/, config.yaml has image_gen.provider: minimax configured, but image_generate tool never works.

Root cause: config.yaml's toolsets list doesn't include "image_gen" — only ["hermes-cli"]. Without the toolset enabled, the tool is never registered to the LLM, no matter how complete the plugin is.

Reproduction: hermes config get toolsets # returns ["hermes-cli"]

Fix: Users must manually run: hermes config set toolsets '["hermes-cli", "image_gen"]'

Issue 2: auxiliary.vision.api_key written to wrong location

Symptom: hermes config set auxiliary.vision.api_key <KEY> succeeds, but vision_analyze still fails with "Auxiliary: marking openrouter unhealthy for 60s", then falls back to a non-vision model.

Root cause: auxiliary_client.py's _try_openrouter() only reads os.getenv("OPENROUTER_API_KEY") (from .env file), NOT config.yaml's auxiliary.vision.api_key. So even when users "correctly" configure vision.api_key, it is never used — instead an empty key triggers an unhealthy mark.

Workaround: Manually write key to .env: OPENROUTER_API_KEY=sk-or-v1-...

Suggested fix: Have hermes config set auxiliary.vision.api_key automatically sync to .env, or raise an error when .env key is not found.

###Issue 3: vision toolset also easy to miss

Symptom: vision tool depends on vision toolset — without it in toolsets, the tool is completely invisible.

Suggestion: Default toolsets should include ["hermes-cli", "image_gen", "vision"], or the installer should auto-detect installed plugins.