docs(acp): correct late-refresh docstring — post-first-turn tools land via between-turns refresh
The claim 'late tools then require an explicit /reload-mcp' was false on current main: the between-turns prologue refresh (agent/turn_context.py) picks up late-connecting servers cache-safely at every turn boundary, and ACP has no /reload-mcp. The daemon's real marginal value is tool-list freshness in the [session created -> first message] window.
This commit is contained in:
parent
23c13589dd
commit
40e0e7ad56
|
|
@ -1055,8 +1055,12 @@ class HermesACPAgent(acp.Agent):
|
|||
Cache safety: the rebuild only runs while the session is still
|
||||
pre-first-turn (no API call made yet → nothing cached to invalidate).
|
||||
Once the user has sent a message we leave the snapshot frozen rather
|
||||
than break the cached prompt prefix mid-conversation; late tools then
|
||||
require an explicit ``/reload-mcp`` (user-consented), exactly as today.
|
||||
than break the cached prompt prefix mid-conversation; servers that land
|
||||
later are picked up cache-safely by the between-turns prologue refresh
|
||||
(``agent/turn_context.py``) at the next turn boundary. The marginal
|
||||
value of this pre-first-turn daemon is therefore freshness in the
|
||||
window [session created → first message] — e.g. the "Available tools"
|
||||
listing a client may request before the first prompt.
|
||||
No-op when discovery already finished, when the join times out, when the
|
||||
registry was unchanged, or when the session was closed while waiting.
|
||||
"""
|
||||
|
|
|
|||
Loading…
Reference in New Issue