liuhao1024 e5bebe2cad fix(plugins): rebuild Honcho client when timeout config changes ...

The Honcho client singleton cached the HTTP timeout at first build.
In long-lived processes (gateway, dashboard), changing the timeout
via config.yaml or HONCHO_TIMEOUT had no effect until restart.

Track the resolved timeout alongside the cached client and compare
on each get_honcho_client() call. When the timeout differs, reset
the singleton so the next call rebuilds with the new value.

Fixes #57347

2026-07-16 22:25:22 -07:00

..

byterover

fix(byterover): honor auto extract config

2026-06-27 04:04:15 -07:00

hindsight

feat(hindsight): configurable embedded daemon health grace timeout (#50341)

2026-06-21 12:20:53 -07:00

holographic

fix(memory): resolve() the shared-connection registry key; symlink test

2026-07-09 18:17:40 -07:00

honcho

fix(plugins): rebuild Honcho client when timeout config changes

2026-07-16 22:25:22 -07:00

mem0

feat(mem0): add self-hosted mode to the setup wizard

2026-07-07 14:07:16 -07:00

openviking

fix(memory): guard local uploads against credential reads

2026-07-05 03:14:49 -07:00

retaindb

fix(memory): guard local uploads against credential reads

2026-07-05 03:14:49 -07:00

supermemory

fix(memory): lazy-install supermemory + mem0 SDKs like honcho/hindsight

2026-06-29 00:25:36 -07:00

__init__.py

fix(dashboard): keep memory.provider in the config schema so Desktop's dropdown survives (#63886)

2026-07-13 18:56:51 -07:00

query_rewrite.py

fix(honcho): enforce recall latency and budget contracts

2026-07-16 12:48:48 -07:00