Files
hermes-skills/autonomous-ai-agents/hermes-agent/references/noris-model-prefix-pitfall.md
T

39 lines
1.2 KiB
Markdown

# Noris / vLLM Model Name Prefix Pitfall
## Problem
When a model name contains a `vllm/` prefix (e.g. `vllm/moonshotai/kimi-k2.6`) inside `model.model` or `model.default`, Hermes resolves it to `noris/vllm/moonshotai/kimi-k2.6`. This fails model catalog lookup because the prefix is interpreted as part of the model string, not a provider qualifier.
## When It Happens
- Profile was previously configured for a **custom/local vLLM endpoint** where `vllm/…` is required
- Later migrated to **Noris (managed provider)** without stripping the prefix
- Any provider where model catalog lookup happens (OpenRouter, Nous Portal, Noris, etc.)
## Fix
Strip the `vllm/` prefix when using a managed provider:
```bash
hermes config set model.model moonshotai/kimi-k2.6
hermes config set model.default moonshotai/kimi-k2.6
```
When using a **custom vLLM endpoint** (e.g. local server on `http://10.0.30.99:8080/v1`), keep the prefix:
```yaml
model:
model: vllm/moonshotai/kimi-k2.6
provider: custom
base_url: http://10.0.30.99:8080/v1
```
## Detection
Check if `hermes config` shows a `vllm/` prefix in the Model line:
```bash
hermes config | grep -E "Model:|model:"
```
If it shows `vllm/` and the provider is Noris/OpenRouter/Nous (not `custom`), strip it.