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
Very interesting framework! I tried implementing something like your "Document Driven Design" a little while back, but this is far and away more sophisticated than what I produced, bravo!
Do you have support for insisting upon a particular structure to the output? Or would that have to be part of a larger prompt passed to the conversate? For example, if I want the agent to reply with text, and give me json key which indicates some serialized documentIDs, so I can render a response appropriately on the client side, how could I implement this?
The text was updated successfully, but these errors were encountered:
PrimoUomo89
changed the title
Feedback for “Agentica > Guide Documents > Core Library > Prompt Histories”
Response type implementation.
Mar 27, 2025
I understand this as a discussion about structured output.
If you're not happy with the agent responding with plain text in the Describe step, you can remove that step.
Also, if you want values to be input in a structured way,
you can enforce this by specifying the types of the functions passed into the controller—
that is, through the generic parameters of typia.llm.application.
When a conversate response is returned, you’ll receive a history.
If you only check the items with the execute type,
you can inspect both the input and output of the functions.
I apologize if I misunderstood your question. Thank you for your interest!
Very interesting framework! I tried implementing something like your "Document Driven Design" a little while back, but this is far and away more sophisticated than what I produced, bravo!
Do you have support for insisting upon a particular structure to the output? Or would that have to be part of a larger prompt passed to the conversate? For example, if I want the agent to reply with text, and give me json key which indicates some serialized documentIDs, so I can render a response appropriately on the client side, how could I implement this?
The text was updated successfully, but these errors were encountered: