Problem
Ollama Cloud (https://ollama.com) is a cloud inference service with OpenAI-compatible API. Currently, users must configure it via custom_providers, but this causes issues:
- The
provider: ollama-cloud setting is not recognized in auxiliary sections
- Workaround requires
provider: custom + redundant base_url + api_key in every auxiliary task config
PROVIDER_REGISTRY in auth.py does not include ollama-cloud
Proposed Solution
Add ollama-cloud to PROVIDER_REGISTRY in hermes_cli/auth.py:
"ollama-cloud": ProviderConfig(
id="ollama-cloud",
name="Ollama Cloud",
auth_type="api_key",
inference_base_url="https://ollama.com/v1",
api_key_env_vars=("OLLAMA_CLOUD_API_KEY",),
),
Also add default auxiliary model in auxiliary_client.py:
_API_KEY_PROVIDER_AUX_MODELS["ollama-cloud"] = "nemotron-3-super"
Benefit
Before (workaround):
auxiliary:
vision:
provider: custom
base_url: https://ollama.com/v1
api_key: xxx
model: qwen3.5:cloud
After (with built-in provider):
auxiliary:
vision:
provider: ollama-cloud
model: qwen3.5:cloud
API key can be set via OLLAMA_CLOUD_API_KEY environment variable or custom_providers entry.
Related
Problem
Ollama Cloud (https://ollama.com) is a cloud inference service with OpenAI-compatible API. Currently, users must configure it via
custom_providers, but this causes issues:provider: ollama-cloudsetting is not recognized inauxiliarysectionsprovider: custom+ redundantbase_url+api_keyin every auxiliary task configPROVIDER_REGISTRYinauth.pydoes not includeollama-cloudProposed Solution
Add
ollama-cloudtoPROVIDER_REGISTRYinhermes_cli/auth.py:Also add default auxiliary model in
auxiliary_client.py:Benefit
Before (workaround):
After (with built-in provider):
API key can be set via
OLLAMA_CLOUD_API_KEYenvironment variable orcustom_providersentry.Related