Hermes Agent v0.11.0 ships Ink TUI rewrite, Bedrock transport, 5 new providers
TL;DR
Hermes Agent v0.11.0 ships a full Ink-based TUI rewrite, a pluggable transport layer with native AWS Bedrock support, five new inference paths, QQBot as a 17th messaging platform, and GPT-5.5 access via Codex OAuth.
What changed
Hermes Agent v0.11.0 (April 23, 2026) ships a full React/Ink rewrite of the interactive CLI with a Python JSON-RPC backend, a pluggable transport layer that extracts format conversion and HTTP from run_agent.py into AnthropicTransport / ChatCompletionsTransport / ResponsesApiTransport / BedrockTransport, native AWS Bedrock via the Converse API, five new inference paths (NVIDIA NIM, Arcee AI, Step Plan, Google Gemini CLI OAuth, Vercel ai-gateway), QQBot as a 17th messaging adapter, and GPT-5.5 access via Codex OAuth. 1,556 commits, 761 merged PRs, 224k insertions across 1,314 files.
Why it matters
The transport ABC is the architectural shift worth paying attention to. Previously every provider lived as branching logic inside run_agent.py; now each transport owns its own format conversion and API shape. That makes adding new providers a plugin operation instead of a core patch, and it is what allowed five new inference paths to land in a single release. Bedrock support specifically opens up enterprise AWS deployments without adding a third-party gateway.
What to watch for
Upgrade is non-breaking; existing profiles continue working as-is. Test the new Ink TUI with hermes --tui if you spend time in interactive sessions. If you run multi-region inference, prototype the Bedrock transport against your existing prompts and compare latency plus per-token cost against your current backend. Watch for the v0.12 release for any further transport consolidations or contracted transports being upstreamed.
Who this matters for
- Developers: Upgrade to v0.11.0 to get the new transport ABC for cleaner provider integrations, native AWS Bedrock via Converse API, and the JSON-RPC TUI gateway. Standard non-breaking upgrade path.
What to watch next
v0.11.0 is the architectural cleanup release Hermes needed before the next wave of providers landed. Pulling format conversion and HTTP transport out of run_agent.py into a transports/ ABC means every new provider now ships as a self-contained plugin instead of a fork in the core inference path. That is the foundation that lets NIM, Bedrock, Arcee, Step Plan, and Vercel ai-gateway all land in one release.
The Ink TUI rewrite is the user-facing headline but the transport ABC is the more durable win. If you maintain a Hermes profile or write skills against it, the JSON-RPC tui_gateway is worth adopting in subagent observability flows. Standard non-breaking upgrade; existing profiles continue working unchanged.
by Harsh Desai
About hermes-agent
View the full hermes-agent page →All hermes-agent updatesMore from hermes-agent
- FeatureHermes Agent v0.4.0 Adds OpenAI API, 6 Messaging Platforms
Hermes Agent v0.4.0 (March 24, 2026) adds an OpenAI-compatible /v1/chat/completions endpoint, six new messaging adapters (Signal, DingTalk, SMS, Mattermost, Matrix, Webhook), @file/@url context, and gateway prompt caching.
- FeatureHermes Agent v0.5.0 Supports 400+ Models, Hardens Supply Chain
Hermes Agent v0.5.0 (March 28, 2026) routes 400+ models via Nous Portal, adds Hugging Face as a first-class provider, removes the compromised litellm dependency, and exposes plugin lifecycle hooks.
- FeatureHermes Agent v0.6.0 Ships Profiles, MCP Mode, Docker Container
Hermes Agent v0.6.0 (March 30, 2026) ships profiles for multiple isolated instances, MCP server mode for Claude Desktop and Cursor, an official Docker image, and ordered fallback provider chains.