<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent Interoperability on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/agent-interoperability/</link><description>Recent content in Agent Interoperability on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 13 Sep 2026 16:15:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/agent-interoperability/index.xml" rel="self" type="application/rss+xml"/><item><title>The Complete Technical Routes for Hermes to Control Claude Code: From Terminal Invocation to Agent Interoperability Protocols</title><link>https://blog.lynxflow.co/en/posts/hermes-claude-code-control-routes-2026/</link><pubDate>Sun, 13 Sep 2026 16:15:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/hermes-claude-code-control-routes-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/hermes-cc-control-routes-cover.png" alt="Featured image of post The Complete Technical Routes for Hermes to Control Claude Code: From Terminal Invocation to Agent Interoperability Protocols" /&gt;One-Sentence Summary Hermes (a Telegram bot gateway) controlling Claude Code (Anthropic&amp;rsquo;s CLI coding agent) has 7 technical routes: direct terminal invocation, SDK programmatic API, MCP bidirectional communication, A2A Agent-to-Agent protocol, ACP Agent Communication protocol, Hooks system, and Cloud sessions. Hermes already has codex_app_server and copilot_acp subprocess runtime templates — adding a Claude Code runtime is essentially copying an existing pattern. For Telegram bot scenarios</description></item></channel></rss>