docs(relay): explain canonical operation migration
Signed-off-by: Alex Fournier <afournier@nvidia.com>
This commit is contained in:
@@ -209,6 +209,25 @@ create a second LLM or tool lifecycle. `tool_parallelism.mode = "observe_only"`
|
||||
keeps tool scheduling observational while still intercepting the core-managed
|
||||
execution boundary.
|
||||
|
||||
### Managed LLM Operation Names
|
||||
|
||||
Hermes identifies managed LLM operations by provider wire protocol, not by the
|
||||
physical service routing the request. This keeps Relay middleware and codec
|
||||
selection stable when providers such as OpenRouter or Nous expose an
|
||||
OpenAI-compatible API:
|
||||
|
||||
| Hermes API mode | Relay operation |
|
||||
| --- | --- |
|
||||
| `chat_completions` | `openai.chat_completions` |
|
||||
| `codex_responses` | `openai.responses` |
|
||||
| `anthropic_messages` | `anthropic.messages` |
|
||||
|
||||
Middleware written against earlier Hermes builds might match physical provider
|
||||
names such as `openrouter`, `nous`, or `anthropic` as the operation. Match the
|
||||
canonical operation instead. Hermes retains the original provider in the
|
||||
managed invocation metadata field `hermes.provider`. Unknown or custom API
|
||||
modes continue to use the physical provider name as their operation.
|
||||
|
||||
### Dynamic Plugins
|
||||
|
||||
Hermes uses the dynamic-plugin activation API available in NeMo Relay 0.6 and
|
||||
|
||||
Reference in New Issue
Block a user