You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every request to the model asks for JSON at the wire: the chat completion
payload carries response_format: {"type":"json_object"} for the
decision, the tidying pass, learn, message, digest and the start-up
probe. A model that answered with a stored fact or a tool result instead
of the decision object did so after a tool call; told at the API level
that only JSON is accepted, it is far less likely to.
message and digest answer inside JSON, {"answer":""} and {"digest":""}, and the daemon reads the field. A prose answer is refused
with no JSON object in model output, counted on the existing error
metric and logged with the first 400 characters of what the model wrote.
A decision object with none of the expected keys, inject, facts or keywords, and a message or digest object without its field, are
refused with an error instead of being read as an empty answer.