mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-06-23 10:42:00 +00:00
fix(image/video gen): make schema delivery instruction platform-neutral (#51031)
* chore: re-trigger CI (workflows did not dispatch on prior head)
* fix(image/video gen): make schema delivery instruction platform-neutral
The image_generate and video_generate tool schema descriptions hardcoded
a gateway-only delivery instruction ('display it with markdown
 and the gateway will deliver it'). That schema
is sent on every platform, so on CLI it directly contradicted the CLI
platform hint ('Do NOT emit MEDIA:/path tags ... state its absolute path
in plain text'), and on messaging platforms it was also wrong about the
mechanism (local file paths are delivered via MEDIA: tags, not markdown
image syntax — markdown ![]() only works for URLs).
The per-platform file-delivery convention is already owned correctly by
the platform hints in prompt_builder.py. The tool schema now just
describes the result shape (URL or absolute path in the image/video field)
and defers 'how to deliver' to the active platform's guidance.
Provider/model injection already works via _build_dynamic_image_schema()
(the 'Active backend: <provider> · model: <model>' line); no change there.
This commit is contained in:
parent
2a58fee1a1
commit
f721d2cda9
2 changed files with 12 additions and 8 deletions
|
|
@ -1184,11 +1184,13 @@ IMAGE_GENERATE_SCHEMA = {
|
|||
"`reference_image_urls` for style/composition references; omit both "
|
||||
"for text-to-image. The underlying backend (FAL, OpenAI, xAI, etc.) "
|
||||
"and model are user-configured and not selectable by the agent. "
|
||||
"Returns either a URL or an absolute file path in the `image` field; "
|
||||
"display it with markdown  and the gateway "
|
||||
"will deliver it. When the active terminal backend has a different "
|
||||
"filesystem, successful local-file results may also include "
|
||||
"`agent_visible_image` for follow-up terminal/file operations."
|
||||
"Returns the result in the `image` field — either a URL or an absolute "
|
||||
"file path. To show it to the user, reference that path/URL in your "
|
||||
"response using the file-delivery convention for the current platform "
|
||||
"(your platform guidance describes how files are delivered here). When "
|
||||
"the active terminal backend has a different filesystem, successful "
|
||||
"local-file results may also include `agent_visible_image` for "
|
||||
"follow-up terminal/file operations."
|
||||
),
|
||||
"parameters": {
|
||||
"type": "object",
|
||||
|
|
|
|||
|
|
@ -419,9 +419,11 @@ _GENERIC_DESCRIPTION = (
|
|||
"endpoint. The backend and model family are user-configured via "
|
||||
"`hermes tools` → Video Generation; the agent does not pick them. "
|
||||
"Long-running generations may take 30 seconds to several minutes — "
|
||||
"the call blocks until the video is ready. Returns either an HTTP "
|
||||
"URL or an absolute file path in the `video` field; display it with "
|
||||
"markdown  and the gateway will deliver it."
|
||||
"the call blocks until the video is ready. Returns the result in the "
|
||||
"`video` field — either an HTTP URL or an absolute file path. To show "
|
||||
"it to the user, reference that path/URL in your response using the "
|
||||
"file-delivery convention for the current platform (your platform "
|
||||
"guidance describes how files are delivered here)."
|
||||
)
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue