From 111ca88fab0cb2019f28c84ac5e1d93865433157 Mon Sep 17 00:00:00 2001
From: k4z4n0v4 <46030560+k4z4n0v4@users.noreply.github.com>
Date: Thu, 25 Jun 2026 10:10:00 +0400
Subject: [PATCH] fix(honcho): honor per-host timeout in config resolution

HonchoClientConfig timeout/requestTimeout resolution skipped the per-host config
block, silently dropping a host-scoped timeout and falling through to the global
config.yaml value (or the default). Add the host block at the front of the
resolution chain, consistent with every other field (base_url, api_key, etc.).
---
 plugins/memory/honcho/client.py | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/plugins/memory/honcho/client.py b/plugins/memory/honcho/client.py
index 271eea63e..a329de334 100644
--- a/plugins/memory/honcho/client.py
+++ b/plugins/memory/honcho/client.py
@@ -457,7 +457,13 @@ class HonchoClientConfig:
             or os.environ.get("HONCHO_BASE_URL", "").strip()
             or None
         )
+        # Host block wins, then flat/global, then env — consistent with every
+        # other field above. Previously the host block was skipped, silently
+        # dropping a per-host `timeout`/`requestTimeout` and falling through to
+        # config.yaml honcho.timeout (or the 30s default).
         timeout = _resolve_optional_float(
+            host_block.get("timeout"),
+            host_block.get("requestTimeout"),
             raw.get("timeout"),
             raw.get("requestTimeout"),
             os.environ.get("HONCHO_TIMEOUT"),