Hermes Agent v0.4.0 Adds OpenAI API, 6 Messaging Platforms

What changed

Hermes Agent v0.4.0 (The Platform Expansion Release) shipped March 24, 2026. Hermes now exposes a drop-in OpenAI-compatible /v1/chat/completions endpoint plus a /api/jobs REST API for cron job management. Six new messaging adapters (Signal, DingTalk, SMS via Twilio, Mattermost, Matrix, generic Webhook) bring the channel count to nine. Claude Code-style @file and @url context references with CLI tab completion inject content into the prompt automatically. Four new providers land: GitHub Copilot via OAuth, Alibaba DashScope, Kilo Code, and OpenCode Zen/Go. Per-session AIAgent gateway cache preserves Anthropic prompt cache across turns; streaming is on by default; 200+ bug fixes ship alongside.

Why it matters

The OpenAI-compatible endpoint converts Hermes from a standalone agent into a backend for any tool or SDK that already speaks OpenAI. Treating Copilot subscriptions as an inference provider lets you reuse credits you are already paying for. Gateway prompt caching across turns materially reduces the cost of long debugging or research sessions where the same context is referenced repeatedly. The expanded messaging surface (now nine channels) means the chat client your team already uses is almost certainly covered.

What to watch for

The OpenAI-compatible API server is opt-in: hermes api serve starts it on a configurable port; existing direct API usage continues unchanged. Validate that any existing code repointed to Hermes still receives the response shape it expects, especially around streaming and tool-call deltas. Confirm that the OAuth flow for GitHub Copilot, DashScope, Kilo Code, and OpenCode Zen completes cleanly in your environment before relying on them as fallbacks.