Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response type implementation. #257

Open
PrimoUomo89 opened this issue Mar 27, 2025 · 2 comments
Open

Response type implementation. #257

PrimoUomo89 opened this issue Mar 27, 2025 · 2 comments
Labels
question Further information is requested

Comments

@PrimoUomo89
Copy link

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?

@PrimoUomo89 PrimoUomo89 changed the title Feedback for “Agentica > Guide Documents > Core Library > Prompt Histories” Response type implementation. Mar 27, 2025
@sunrabbit123
Copy link
Collaborator

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!

@kakasoo kakasoo added the question Further information is requested label Mar 28, 2025
@kakasoo
Copy link
Contributor

kakasoo commented Mar 28, 2025

Also, If you're curious about the code, give me an example and it's even better. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants