David/HERMES-GIELIE
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Drop persist_user_timestamp kwarg for older hermes-agent compatibility

Browse source 
The pinned hermes-agent@sha256:2f1f2f1... doesn't support
persist_user_timestamp in AIAgent.run_conversation(). The webui
expects this parameter, so any prompt fails with:
  TypeError: AIAgent.run_conversation() got an unexpected keyword
  argument 'persist_user_timestamp'

Same pattern as the existing moa_config workaround above each call
site: drop the kwarg, accept the feature gap (timestamp not persisted
on user messages) until the agent is bumped to a version that adds
the parameter.

Co-authored-by: Orca <help@stably.ai>
This commit is contained in:
Pi Agent 2026-08-05 17:07:09 +02:00
parent eb8da48144
commit 07ce1279fa
1 changed files with 0 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
api/streaming.py
View file

@ -9555,7 +9555,6 @@ def _run_agent_streaming(
),
task_id=session_id,
persist_user_message=msg_text,
persist_user_timestamp=getattr(s, 'pending_started_at', None),
)
# Only pass moa_config when a /moa override is actually active, so a
# normal send never trips a TypeError on an older hermes-agent whose
@ -10039,7 +10038,6 @@ def _run_agent_streaming(
),
task_id=session_id,
persist_user_message=msg_text,
persist_user_timestamp=getattr(s, 'pending_started_at', None),
)
if moa_config is not None:
_heal_kwargs["moa_config"] = moa_config
@ -11263,7 +11261,6 @@ def _run_agent_streaming(
),
task_id=session_id,
persist_user_message=msg_text,
persist_user_timestamp=getattr(s, 'pending_started_at', None),
)
if moa_config is not None:
_heal_kwargs2["moa_config"] = moa_config