Hermes Agent's custom provider configuration lets you connect to LongCat-2.5 through LongCat's OpenAI-compatible API.
Suitable tasks: Running automation tasks and terminal interactions with LongCat-2.5 in Hermes Agent.
Unsuitable tasks: Treating this configuration as a task prompt or an evaluation of model performance.
Supported model version: LongCat-2.5.
Supported client, agent, or API: Hermes Agent; LongCat OpenAI-compatible API.
Recommended reasoning level and parameters: Not specified.
Edit ~/.hermes/config.yaml, replacing the placeholder with your own LongCat API key:
model:
provider: custom
base_url: https://api.longcat.chat/openai/v1
api_key: <Your LongCat API Key>
default: LongCat-2.5You can also use hermes config set to set the four fields above individually; model.provider must be custom. Do not put a real key in shared documents or code repositories.
Install Hermes Agent and run hermes --version to confirm the installation. The officially listed systems are Linux, macOS, and WSL2; Windows users must work in WSL2.
Get an API key from LongCat Platform and confirm that your account has sufficient credits.
Configure ~/.hermes/config.yaml as described above, then run hermes doctor to check the configuration.
Open a new terminal and run hermes, or run hermes --tui to start TUI mode. The source uses the conversation interface opening normally as the startup check.
The official model table lists LongCat-2.5 and the OpenAI/Anthropic API formats.
The Hermes Agent integration example uses the custom provider, https://api.longcat.chat/openai/v1, and LongCat-2.5.
The source provides no performance test data or task outputs.
This is an official integration configuration; it does not demonstrate performance on any particular task. The page does not specify the Hermes Agent version, reasoning level, or sampling parameters. Actual API and client behavior may change across versions.
You need Hermes Agent installed, a LongCat API key, and sufficient credits. Follow the steps to configure and launch it. This entry is based on the official documentation; the API was not called for verification.
LongCat 2.5