Hermes Turbo Agent

🌍 Languages: 🇬🇧 English | 🇧🇷 Português | 🇪🇸 Español | 🇫🇷 Français | 🇩🇪 Deutsch | 🇮🇹 Italiano | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇨🇳 简体中文 | 🇷🇺 Русский | 🇵🇱 Polski | 🇮🇳 हिन्दी | 🇸🇦 العربية | 🇮🇱 עברית | 🇮🇩 Bahasa Indonesia | 🇲🇾 Bahasa Melayu

Executable installation and performance-optimization skill for Hermes Agent. It is a procedure, not an executable fork: it measures the active Hermes path, applies the smallest compatible change, tests it, and keeps it only when evidence supports it.

1. Scope and safety

The target is the active bundle at ${HERMES_HOME:-$HOME/.hermes}. The skill must not silently modify a source checkout, discard user state, break prompt caching, add telemetry, or claim a benchmark gain that was not measured on the real path.

Every run creates a rollback point, records a baseline, applies a bounded change, runs regression tests, repeats the benchmark, and reports modified files, fallback status, and rollback instructions.

2. Performance modules

Fast JSON and typed contracts

Use an internal bytes-first adapter with this order:

1. orjson for ordinary JSON dictionaries, lists, tool results, and cache payloads;
2. msgspec only for stable typed Struct contracts such as fixed envelopes;
3. Python json as the universal fallback.

The adapter must preserve str/bytes behavior, Unicode, invalid-payload errors, non-serializable values, and compatibility with existing dictionaries. It must never replace flexible parsing with a typed contract without tests.

Native streaming parser

The Simplicio Agent comparison added a PyO3 hermes_fast extension for incremental JSON/tool-call parsing. Hermes Turbo may build it with maturin, but it remains optional and must have a json.JSONDecoder.raw_decode fallback.

The FFI boundary is not free. On the measured macOS Python 3.11 path, small payloads were faster with stdlib; payloads around 1 KiB and larger favored Rust. Use a target-specific size threshold and re-benchmark after changing Python, Rust, or the extension.

Async event loop