Hermes Agent Integration Overview
Hermes has three different Ace Data Cloud product routes. Their credentials, configurations, and validation scopes cannot be substituted for one another.
| Route | Guide | Status |
|---|---|---|
hermes model interactive wizard |
Wizard | Verified configuration contract |
YAML + .env manual configuration |
Manual | Verified configuration contract |
| Ace Data Cloud managed deployment | Management page deployment | Verified platform route; availability scope is subject to the console |
Managed deployment is managed by platform credentials, Provider configuration, and persistent instances, without requiring users to paste Tokens. The platform deployment template will configure the Ace Data Cloud Provider, model, and credentials for Hermes, and save instance data to persistent volumes.
¶ Managed Deployment Validation
- Create a Hermes deployment in application management and select a model.
- Wait for the instance to enter Ready.
- Open the Hermes Dashboard and send
Reply only OK. - Execute the tool call or code task again.
- Confirm whether to export persistent data before deleting the deployment; deleting the instance will process associated storage as prompted by the console.
Currently, the local configuration uses providers: with the config-v12 named provider and explicit transport: chat_completions. The model ID is based on the model directory and does not maintain a static "all models" commitment.
Return to the Coding Plan Configuration Center.